Ah, ok. after doing a database commit I get the error going to stderr. Now it's just a matter of capturing/redirecting the stderr output and using an except there. Thanks. Mark
On Friday, October 03, 2014 11:35:08 PM you wrote: > the sqlite3 command line doesn't require a commit, it gave an error after > the attempted insert command. > > pysqlite requires one? > > Mark > > On Friday, October 03, 2014 09:06:56 PM Keith Medcalf wrote: > > Are you committing the change? > > > > >-----Original Message----- > > >From: [email protected] [mailto:sqlite-users- > > >[email protected]] On Behalf Of Mark Halegua > > >Sent: Friday, 3 October, 2014 20:58 > > >To: [email protected] > > >Subject: [sqlite] passing error messages to pysqlite > > > > > >I have a sqlite3 database. In the networkied are I have the db is locked > > >(wee've > > >discussed this before, and I'm using it mostly on a local machine, but I > > >need to > > >test certain conditions, networking being one). > > > > > >In the sqlite3 command line, when I try to insert new info I get a dabase > > >locked > > >message. > > > > > >Hosever, when I do the same in python with pysqlite, it doesn't return > > >anything > > >and the code proceeds as if nothing happened, and the program just goes > > >on, > > >even though the data wasn't saved/ > > > > > >I'm sure some message is being returned to pysqlite, how do I capture it > > >to set up > > >an error trap/condition? > > > > > >Thanks > > >_______________________________________________ > > >sqlite-users mailing list > > >[email protected] > > >http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > > > > _______________________________________________ > > sqlite-users mailing list > > [email protected] > > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
