On Oct 30, 2008, at 2:45 PM, Michele Simionato wrote:
> > On Oct 30, 7:18 pm, Michael Bayer <[EMAIL PROTECTED]> wrote: >> we dont parse DDL but instead only read Table objects from the >> database directly, using reflection via the "autoload=True" flag. If >> you had a DDL file, you could load this into a database to be >> reflected, else if you already have a live database, you can reflect >> straight from that. >> >> docs are here: >> >> http://www.sqlalchemy.org/docs/05/ >> metadata.html#metadata_tables_refle... >> >> but also, this seems to be missing from the docs there, metadata can >> reflect the entire database using: >> >> metadata.reflect(bind=someengine) > > Does the reflection of UNIQUE constraints work? reflection of UNIQUE and CHECK constraints and other indexes is generally not implemented since SQLAlchemy does not make use of these except when issuing DDL - only foreign key constraints affect the operation of SQLA outside of DDL generation. The MySQL dialect has the most support for reflection of indexes and various constraints. I don't think its present for any of the other dialects, though. We're of course open to accepting patches for that level of functionality. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
