From: | Dmitriy Igrishin <dmitigr(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org, Alexander Farber <alexander(dot)farber(at)gmail(dot)com> |
Subject: | Re: A cronjob for copying a table from Oracle |
Date: | 2010-12-10 18:03:25 |
Message-ID: | AANLkTi=3vCnJnXhWY22DE2-v4s-CyF-T5=koXK2FXJO1@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
2010/12/10 Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>
> On 12/10/2010 09:45 AM, Dmitriy Igrishin wrote:
>
>> Huh! Yes, indeed ! But how is it possible ?! I see
>> EMAIL = _EMAIL,
>> EMAILID = _EMAILID,
>>
>> rather than
>>
>> EMAIL = $7,
>> EMAILID = $8,
>>
>> in the function definition...
>>
>
> My guess the reversal is taking place in the PHP code. The table definition
> and the argument list to the Pg function have one order for emailid,email
> and the update and insert statements have another; email,emailid. I would
> guess that the PHP is building the row variables using the SQL statement
> order and than passing that to the Pg function which has a different order.
>
Yeah, thats why I've asked the OP to post SQL with call of the function (in
PHP).
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)gmail(dot)com
>
--
// Dmitriy.
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2010-12-10 18:05:44 | Re: Extended query protocol and exact types matches. |
Previous Message | Adrian Klaver | 2010-12-10 18:01:18 | Re: A cronjob for copying a table from Oracle |