On Friday 28 July 2006 11:13, Oleg Broytmann wrote:
> > I've discovered that the Database API Specification v2.0 is followed
> > by both MySQL and
> > SQLite Python modules, so all that need to be done in this case was a
> > one-to-one mapping between
> > their exceptions and the SQLObject defined
Hello!
On Thu, Jul 27, 2006 at 08:39:02PM +0300, Dan Pascu wrote:
> Following the discussion we had about 2 months ago about having sqlobject
> raise a set of exceptions independent of the backend used, I asked a
> colleague of mine to implement this.
> He did it for the mysql and sqlite backend
Dan Pascu <[EMAIL PROTECTED]> writes:
> Following the discussion we had about 2 months ago about having sqlobject
> raise a set of exceptions independent of the backend used, I asked a
> colleague of mine to implement this.
This sounds like a very good idea to me!
I'm currently using a sqlite
Following the discussion we had about 2 months ago about having sqlobject
raise a set of exceptions independent of the backend used, I asked a
colleague of mine to implement this.
He did it for the mysql and sqlite backends, for which we have experience.
Not having any experience with the other
