From: briot.emmanuel@gmail.com
Subject: Re: GNATCOLL SQLite rollback vs cursor
Date: Fri, 31 Aug 2012 05:10:51 -0700 (PDT)
Date: 2012-08-31T05:10:51-07:00 [thread overview]
Message-ID: <fb6d3e36-2987-425a-ad33-73df7bdb348b@googlegroups.com> (raw)
In-Reply-To: <85ipbzwdsc.fsf@stephe-leake.org>
It is quite possible that this issue has in fact already been fixed in the development version of GNATCOLL, because now with or without the line that frees the cursor, the result is the same:
Insert Ada Lovelace
ID => 1
Insert Charles Babbage
ID => 2
Insert Ada Lovelace
[SQL.ERROR] Failed to execute INSERT INTO Author (First, Last) VALUES ("Ada", "Lovelace") error=columns First, Last are not unique
ID => 1
Insert Grace Hopper
ID => 3
Note also that we have improved the way we retrieve the error messages from sqlite, since the current one is clearer than just the "constraint error" you are getting.
Emmanuel
next prev parent reply other threads:[~2012-08-31 12:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-31 10:34 GNATCOLL SQLite rollback vs cursor Stephen Leake
2012-08-31 12:10 ` briot.emmanuel [this message]
2012-09-01 16:31 ` Stephen Leake
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox