From: | Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk> |
---|---|
To: | Dave Cramer <dave(at)fastcrypt(dot)com> |
Cc: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: request for sql3 compliance for the update command |
Date: | 2003-02-19 20:02:47 |
Message-ID: | 20030219200247.E5614@quartz.newn.cam.ac.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Feb 19, 2003 at 07:31:35AM -0500, Dave Cramer wrote:
> Bruce,
>
> Can you chime in with your support here?
>
> Dave
>
> I have a large customer who is converting from informix to postgres and
> they have made extensive use of
>
> update table set (col...) = ( val...)
>
> as a first pass would it be possible to translate this in the parser to
>
> update table set col=val
>
> It would appear that this is SQL3 compliant
>
> <set clause> ::=
> <update target> <equals operator> <row value designator>
>
> <update target> ::=
> <object column>
> | <left paren> <object column list> <right paren>
>
>
> or can someone think of another way?
I don't understand the original problem. What does informix give you? A
text file full of "update table set ()=()" which you then try to feed
into postgres? In that case, why not pass said text file through a sed or
perl script first?
Cheers,
Patrick
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2003-02-19 20:18:01 | Re: request for sql3 compliance for the update command |
Previous Message | Tom Lane | 2003-02-19 19:12:53 | Re: request for sql3 compliance for the update command |