FYI I figured what was the problem. The database log level was changed
to FATAL from ERROR (default?).
On Wed, Jun 17, 2009 at 1:04 PM, Dennis Brakhane<brakhane(at)googlemail(dot)com> wrote:
> On Wed, Jun 17, 2009 at 9:57 PM, Ivan Bojer<ibojer(at)gmail(dot)com> wrote:
>> I have a table with UNIQUE constraint on the column. Inserting 2 of
>> same values on it fails (as it should)
>> and I can see DBLog Error message. Alas, there is no exception thrown
>> from JDBC so that I can properly
>> handle it.
> This is from memory, so if I talk nonsense, I hope somebody corrects me.
> The exception thrown should be a SQLException. These have a
> "getSQLState" method which returns a string. If this string is
> "23505", you have a UNIQUE violation.
> You can see the possible error codes here:
In response to
pgsql-jdbc by date
|Next:||From: Thomas Finneid||Date: 2009-06-19 10:37:15|
|Subject: Connection exceptions|
|Previous:||From: Dennis Brakhane||Date: 2009-06-17 20:05:36|
|Subject: Re: Please help! - Constraints Exception|