can you please report this as a bug in MySQL 1.2.3b1. The exception raised looks like this in pdb:
ProgrammingError(ProgrammingError(1146, "Table 'test.t1' doesn't exist"),) i.e., it raises a ProgrammingError, where first argument is in fact another instance of ProgrammingError. We can work around this in the MySQL dialect but I would rather wait until a final version of 1.2.3 is released, hopefully with this bug fixed. this is how it should look: ProgrammingError(1146, "Table 'test.t1' doesn't exist") (Pdb) e.args (1146, "Table 'test.t1' doesn't exist") On Mar 6, 2009, at 6:13 AM, Ben Cheng wrote: > > Hi, > > I'm not sure is it a bug of SQLAlchemy or MySQL-Python, may some one > advice or if you know any related tickets? > > When I'm using SQLAlchemy on MySQL-Python 1.2.3, it shows error on the > following SQL when I call create_all: > > 19:05:33,895 INFO [sqlalchemy.engine.base.Engine.0x...a0f0] SHOW > VARIABLES LIKE 'sql_mode' > 19:05:33,895 INFO [sqlalchemy.engine.base.Engine.0x...a0f0] () > 19:05:33,934 INFO [sqlalchemy.engine.base.Engine.0x...a0f0] DESCRIBE > `forms` > 19:05:33,935 INFO [sqlalchemy.engine.base.Engine.0x...a0f0] () > 19:05:33,947 INFO [sqlalchemy.engine.base.Engine.0x...a0f0] ROLLBACK > > sqlalchemy.exc.ProgrammingError: (ProgrammingError) (1146, "Table > 'voters.forms' doesn't exist") 'DESCRIBE `forms`' () > > But when I roll-back to MySQL-Python 1.2.1, the error gones. > > Any thought? > > Best, > Ben > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
