oh, except you might have problems with tables in there that are reflected due to a foreign key. Table is not really intended for subclassing, unless you want to do SQLAlchemy-Migrate's approach of monkeypatching Table.__bases__ at the global level, I'd seek some other way to achieve what you want.
On Jul 31, 2013, at 1:56 PM, Michael Bayer <[email protected]> wrote: > You'd probably implement your own reflect_all function/method: > > from sqlalchemy import inspect > > def reflect(metadata, bind): > inspector = inspect(bind) > for tname in inspector.get_table_names(): > MySpecialTable(tname, metadata, autoload=True, autoload_with=bind) > > > > On Jul 31, 2013, at 1:34 PM, tiadobatima <[email protected]> wrote: > >> Hello there, >> >> When this application starts, we reflect the DB into a MetaData() object and >> this is made available for everyone to use. >> I'd like to add a few more methods to the table objects within that >> MetaData(). Is there any easy way to extend these already instantiated >> sqlalchemy.schema.Table objects? >> >> Thanks! :) >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "sqlalchemy" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/sqlalchemy. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >
signature.asc
Description: Message signed with OpenPGP using GPGMail
