Re: [Sqlalchemy-users] strange initialization problem with latest trunk

2006-06-26 Thread Brad Clements
On 26 Jun 2006 at 15:30, Michael Bayer wrote: > I made a change that should fix this in changeset 1660. It appears to be fixed, thanks -- Brad Clements,[EMAIL PROTECTED](315)268-1000 http://www.murkworks.com AOL-IM or SKYPE: BKClements Using To

Re: [Sqlalchemy-users] strange initialization problem with latest trunk

2006-06-26 Thread Michael Bayer
I made a change that should fix this in changeset 1660. On Jun 23, 2006, at 3:21 PM, Brad Clements wrote: > On 22 Jun 2006 at 23:44, Michael Bayer wrote: > >> a lot has changed with mapper initialization (and plenty of >> bugs), but not tables. can you send a test example ? > > Sorry my exa

Re: [Sqlalchemy-users] strange initialization problem with latest trunk

2006-06-23 Thread Brad Clements
On 22 Jun 2006 at 23:44, Michael Bayer wrote: > a lot has changed with mapper initialization (and plenty of > bugs), but not tables. can you send a test example ? Sorry my example was not clear. the variable is called 'table' in my module, but it is a mapper. from P2P.database.dbtables.

Re: [Sqlalchemy-users] strange initialization problem with latest trunk

2006-06-22 Thread Michael Bayer
a lot has changed with mapper initialization (and plenty of bugs), but not tables. can you send a test example ? heres a session with tables: >>> from sqlalchemy import * >>> meta = MetaData() >>> t = Table('sometable', meta, Column('col1', Integer, primary_key=True), Column ('col2',

[Sqlalchemy-users] strange initialization problem with latest trunk

2006-06-22 Thread Brad Clements
I have code that's been working with an earlier version of 0.2 after svn up tonight I find this odd behaviour, that is table.c is busted until the first query is executed. Then that table starts working, but other tables are broken too until I perform a select on them. Revision: 1654 -- I