From: | list_usr(at)spacebox(dot)net |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Kris Jurka <books(at)ejurka(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Column is of type date but expression is of type text |
Date: | 2010-02-21 20:32:47 |
Message-ID: | 1e11c2271002211232v6a932ba5kf687180cd3b12f27@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
But wouldn't the stored procedure with parameters matching the order
of the parameters in the call be the stored procedure to be called?
On Sun, Feb 21, 2010 at 1:17 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> list_usr(at)spacebox(dot)net writes:
>> I think the issue was the ordering of the parameters - after your
>> initial answer to my question I updated the stored procedure so the
>> ordering of the parameters matched the order that they appeared in the
>> insert statement. I recreated the stored procedure and continued to
>> encounter the problem which led me to believe that wasn't the issue.
>
> Note that two functions with the same names and differently ordered
> parameter lists are different objects to Postgres. I think maybe you
> forgot to drop the first version and it was still getting invoked.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-02-21 22:24:20 | Re: Column is of type date but expression is of type text |
Previous Message | Tom Lane | 2010-02-21 18:17:51 | Re: Column is of type date but expression is of type text |