On Aug 21, 2007, at 8:21 PM, johnf wrote:
> So I kept digging and created a test case. And in fact I see an
> update
> statement then a commit - which produces an error. Then it
> occurred to me
> that something could be wrong with the framework. Which is why I
> continue
> the discussion.
You missed the part where I explained that it is a logging issue:
"OK, I've looked into this, and have fixed a couple of small things,
but one big fact remains: that *any* failed execute(), even one
wrapped in a try/except, will generate the dbActivityLog output for
"FAILED SQL", since that appears as the first line of the except
block. It re-raises the exception, where the try/except block in
dbSQLite.commitTransaction() catches it and handles it properly."
Since there is no way to tell if SQLite is in the middle of a
transaction or not, we try to commit, and if we fail, we trap that
and continue on. The only issue is whether the error message is a
problem or not. I'm actually working right now on a way to silence
the log message in certain cases just like this one.
-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
Searchable Archives: http://leafe.com/archives/search/dabo-dev
This message: http://leafe.com/archives/byMID/dabo-dev/[EMAIL PROTECTED]
