On Sep 2, 2007, at 9:27 AM, Orest Kozyar wrote:
> > Is the SQLAlchemy "reflect" command just not designed to pick up these > unique constraints, or is there something I am missing? > reflection currently does not *consistently* pick up things like unique constraints, check constraints, or indexes....i say "consistently" because some efforts have been made to add some of these things to the MySQL and Postgres dialects (although i think the postgres ones might just be trac tickets)...but it generally does not. The reason these things aren't reflected is becasue SQLAlchemy doesn't use them for anything except CREATE TABLE statements, and the idea was that if youre reflecting, the table is obviously already created. But now people are getting into "copying" table defs across databases, so people are asking for stuff like this. While I dont consider this to be a core goal of SQLAlchemy, we have been accepting patches for these things provided they dont negatively impact reflection performance or stability. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
