Re: [sqlalchemy] NameError: global name 'exc' is not defined (0.6beta3)

2010-04-08 Thread David Gardner
Thanks, I took a clone from hg, and all of my unit tests are passing now, and 0.6 is working great. I ran into one instance (I don't think this is a bug) where session.expire_all() didn't clear out an object after a call to Query.delete(synchronize_session=False), but I found that using

[sqlalchemy] NameError: global name 'exc' is not defined (0.6beta3)

2010-04-07 Thread David Gardner
I was testing 0.6beta3 with my code and I ran into a problem when retrieving columns from a joined table. It appears that it occurs when the object inherits from an object which also inherits from another object all using joined table inheritance. from asset.farm.farmdb import *

Re: [sqlalchemy] NameError: global name 'exc' is not defined (0.6beta3)

2010-04-07 Thread David Gardner
Spent a little more time with this one, the problem seems to be autoload-ing a table that has an array of reals like: CREATE TABLE test_tbl ( pk integer NOT NULL, newcol text, real_array real[], CONSTRAINT test_tbl_pkey PRIMARY KEY (pk) ) WITH ( OIDS=FALSE ); ALTER TABLE test_tbl OWNER

Re: [sqlalchemy] NameError: global name 'exc' is not defined (0.6beta3)

2010-04-07 Thread Michael Bayer
these issues are all repaired as of r9b02710ca3b3. David Gardner wrote: Spent a little more time with this one, the problem seems to be autoload-ing a table that has an array of reals like: CREATE TABLE test_tbl ( pk integer NOT NULL, newcol text, real_array real[],