Re: [Sqlalchemy-users] raise from mysql

2006-07-15 Thread Mike Bernson
This did fix the problem Michael Bayer wrote: > oh, on connect. OK, i just wrapped that in DBAPIError(SQLAlchemyError) > if you try out rev 1706. > > > On Jul 13, 2006, at 3:48 PM, Mike Bernson wrote: > >> Here is the small program and it run. >> >> >> from sqlalchemy import * >> >> from _mysq

Re: [Sqlalchemy-users] raise from mysql

2006-07-13 Thread Michael Bayer
oh, on connect. OK, i just wrapped that in DBAPIError (SQLAlchemyError) if you try out rev 1706. On Jul 13, 2006, at 3:48 PM, Mike Bernson wrote: > Here is the small program and it run. > > > from sqlalchemy import * > > from _mysql_exceptions import OperationalError > > > class db(object): >

Re: [Sqlalchemy-users] raise from mysql

2006-07-13 Thread Mike Bernson
Here is the small program and it run. from sqlalchemy import * from _mysql_exceptions import OperationalError class db(object): def __init__(self): connect_string = "mysql://mike:[EMAIL PROTECTED]/abc" engine = create_engine(connect_string,

Re: [Sqlalchemy-users] raise from mysql

2006-07-13 Thread Michael Bayer
youll have to show me how youre getting that result. all the exceptions raised by the database should be wrapped in a SQLAlchemyError. On Jul 13, 2006, at 3:30 PM, Mike Bernson wrote: > I am trying to write application that does not care which database > it is > connecting to. It uses the

[Sqlalchemy-users] raise from mysql

2006-07-13 Thread Mike Bernson
I am trying to write application that does not care which database it is connecting to. It uses the connect string to choose the database. Thing look good until I get an error from mysql which is a raise on mysql classes. Should the raises come from an sqlalchemy class so that I get the same type