2006/1/11, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
> i just wanted to clarify since i realized that
> the 'columns' in my example was rather ambiguous.
>
> On Jan 10, 2006, at 5:19 PM, [EMAIL PROTECTED] wrote:
> > engine = create_engine('...')
> > c = engine.ischema.columns
> > c.select(c.c.table_name=='foo')
>
> what i mean here is that 'c' is the *Table*
> information_schema.columns. therefore 'c.c'
> refers to the columns of this table.
> the implementation would use minor property
> magic to do the tbl = gen_tbl.toengine(engine)
> work that is done explicitly in reflecttable.
>What you want is only suit for legacy schema. Because that if you want to create new table in database, you should properly write a Table Metadata module to create your schemas, and this module can be used laterly. And against the legacy schema, if you just want to use autoload feature, there maybe lack many relationships and foreign keys definition. So I think that also defining Table Metadata maybe better. -- I like python! My Blog: http://www.donews.net/limodou NewEdit Maillist: http://groups.google.com/group/NewEdit ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Sqlalchemy-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
