DatabaseError() to be specific...
Posted: Tue Jan 15, 2013 6:38 am
When working with threaded programs, it would be nice if there was a way to track databseerror() a bit better.
if two threads perform a query, and one errors out, you don't know which thread is the one from DatabaseError() is referencing.
Since things like DatabaseUpdate() and DatabseQuery() don't return a file handle, it would make it hard to track; and using mutex's defeats the purpose of the threads... Especially if they are working on completely different databases... So no idea on best way to deal with; but someway would be better...
(iow I have no idea how to implement it, but fetching the error specific to a call would be better than getting it for "some call")
if two threads perform a query, and one errors out, you don't know which thread is the one from DatabaseError() is referencing.
Since things like DatabaseUpdate() and DatabseQuery() don't return a file handle, it would make it hard to track; and using mutex's defeats the purpose of the threads... Especially if they are working on completely different databases... So no idea on best way to deal with; but someway would be better...
(iow I have no idea how to implement it, but fetching the error specific to a call would be better than getting it for "some call")