Ed Leafe wrote:
> On Aug 21, 2007, at 5:23 PM, Paul McNett wrote:
>
>> Yeah, I just wanted to counter Ed's statement that it would be
>> impossible to fix. I see the word 'impossible' and some instinct
>> inside
>> me says 'has to be possible'. ;)
>
> When did I say it would be impossible to fix? I only said that you
> cannot determine the transaction status of SQLite.
You could argue that I misremembered your statement:
"""
There is no way to test ahead of time in SQLite as to whether a
transaction exists or not, so the only way to deal with this is to
wrap the call to "COMMIT" in a try/except block, as we are doing.
"""
I see that you were saying there's no way to test ahead of time, not
that there's no way to selectively suppress the log entry, however
taking it in context with your previous paragraph:
"""
My question to you is whether this is a problem for you. It is
working exactly as expected, but if having those "FAILED SQL"
messages in your logs looks wrong, I could remove the logging, but
then you wouldn't have a log message when a query actually failed.
"""
I guess I interpreted it to mean that we either needed to suppress the
log always or live with the spurious entries.
--
pkm ~ http://paulmcnett.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]
