I saw a discussion from late 2006 about the possibility of propagating the SQLite error codes back up when throwing a SQLException. Did anything happen with this?
When I violate a UNIQUE constraint, e.getErrorCode()is 0 [that's where MySQL's Connector/J puts its error code] and e.getSQLState() is null [that's where Derby puts its error code]. I need to be able to differentiate between this expected, recoverable case and a real error... --~--~---------~--~----~------------~-------~--~----~ Mailing List: http://groups.google.com/group/sqlitejdbc?hl=en To unsubscribe, send email to [EMAIL PROTECTED] -~----------~----~----~----~------~----~------~--~---
