So I don't know what happened.. but I dropped the database and
reloaded it and now it works. I had made some small updates to the
stored procedure but had been recreating it (CREATE OR REPLACE
FUNCTION) with the updates - should I have been restarting Postgres
after recreating the stored procedure?
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.
Anyhow, after recreating the database it's now working.
Thanks for all your help!
-- Matt
On Sat, Feb 20, 2010 at 2:21 PM, Kris Jurka <books@ejurka.com> wrote:
>
>
> On Fri, 19 Feb 2010, list_usr@spacebox.net wrote:
>
>> Re: version, good question - I have both postgresql-8.4-701.jdbc3.jar
>> and postgresql-8.4-701.jdbc4.jar in my Apache Tomcat 5.5 common/lib
>> directory. Would that cause a problem?
>>
>> I'm using PostgreSQL 8.4. Java 1.6.
>>
>> Your example code worked with both jdbc3 and jdbc4, but my code still
>> isn't working.
>
> Well those versions are all recent enough not to have any problems. If my
> code works and yours doesn't it's likely you're not telling us something
> about your code. If you can create a self-contained testcase like I did
> then I'd be happy to look at it, but it doesn't look like a driver problem.
>
> Kris Jurka
>
