Skip Menu |

This queue is for tickets about the DBD-SQLite CPAN distribution.

Report information
The Basics
Id: 123342
Status: resolved
Priority: 0/
Queue: DBD-SQLite

People
Owner: Nobody in particular
Requestors: dmuey [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: $dbh->err() only returns generic Primary Result Code List (i.e not more specific Extended Result Code) :/
If you use $dbh->do("INSERT …") to insert a row that violates a unique column constraint then $dbh->err() is 19 (SQLITE_CONSTRAINT) not 2067 (SQLITE_CONSTRAINT_UNIQUE) Is there a way to get err() to support more specific codes (i.e. “Extended Result Code” per https://sqlite.org/rescode.html)? perl v5.16.0, DBI v1.631, DBD::SQLite v1.54 thanks!
Can we expose `sqlite3_extended_result_codes()` (https://sqlite.org/c3ref/extended_result_codes.html) like we do `sqlite3_create_function()` (https://sqlite.org/c3ref/create_function.html)? e.g. just like we can use the c library’s $dbh->sqlite_create_function(…) we could $dbh->sqlite_extended_result_codes(1).
On Thu Oct 26 06:03:32 2017, DMUEY wrote: Show quoted text
> Can we expose `sqlite3_extended_result_codes()` > (https://sqlite.org/c3ref/extended_result_codes.html) like we do > `sqlite3_create_function()` > (https://sqlite.org/c3ref/create_function.html)? > > e.g. just like we can use the c library’s $dbh-
> >sqlite_create_function(…) we could $dbh- > >sqlite_extended_result_codes(1).
Sorry for the delay. It turns out it has been implemented since DBD::SQLite 1.48, by the commit: https://github.com/DBD-SQLite/DBD-SQLite/commit/b1975f1e9787b1412a5b143a82351b50900fc4c6 , though not documented. See the test for usage. I'll add some documentation. Does this suffice?
On Tue Nov 21 04:03:26 2017, ISHIGAKI wrote: Show quoted text
> On Thu Oct 26 06:03:32 2017, DMUEY wrote:
> > Can we expose `sqlite3_extended_result_codes()` > > (https://sqlite.org/c3ref/extended_result_codes.html) like we do > > `sqlite3_create_function()` > > (https://sqlite.org/c3ref/create_function.html)? > > > > e.g. just like we can use the c library’s $dbh-
> > > sqlite_create_function(…) we could $dbh- > > > sqlite_extended_result_codes(1).
> > > Sorry for the delay. It turns out it has been implemented since > DBD::SQLite 1.48, by the commit: https://github.com/DBD-SQLite/DBD- > SQLite/commit/b1975f1e9787b1412a5b143a82351b50900fc4c6 , though not > documented. See the test for usage. I'll add some documentation. Does > this suffice?
Added a note on the handle attribute and shipped 1.55_04.
That is perfect!!! Thanks :) I'll update it and try it out ASAP!!! On Mon Nov 20 14:03:26 2017, ISHIGAKI wrote: Show quoted text
> On Thu Oct 26 06:03:32 2017, DMUEY wrote:
> > Can we expose `sqlite3_extended_result_codes()` > > (https://sqlite.org/c3ref/extended_result_codes.html) like we do > > `sqlite3_create_function()` > > (https://sqlite.org/c3ref/create_function.html)? > > > > e.g. just like we can use the c library’s $dbh-
> > > sqlite_create_function(…) we could $dbh- > > > sqlite_extended_result_codes(1).
> > > Sorry for the delay. It turns out it has been implemented since > DBD::SQLite 1.48, by the commit: https://github.com/DBD-SQLite/DBD- > SQLite/commit/b1975f1e9787b1412a5b143a82351b50900fc4c6 , though not > documented. See the test for usage. I'll add some documentation. Does > this suffice?
On Mon Nov 27 10:05:14 2017, DMUEY wrote: Show quoted text
> That is perfect!!! Thanks :) > > I'll update it and try it out ASAP!!!
worked like a champ, thanks!
Closed. Thanks.