Michael, Thanks for explaining this.
It's a bug in Elixir, which passes the user specified name for the constraint *alongside* the constraint name that it generates rather than instead of. I've now fixed this, but is there a way to specify the names of the indexes generated; these are also too long. Regards, Tim On Apr 14, 11:05 pm, Michael Bayer <[EMAIL PROTECTED]> wrote: > On Apr 14, 2008, at 1:54 PM, Dr.T wrote: > > > > > It is possible specify the name of a Foreign Key Constraint generated > > by a foreign key column specification? > > > Looking at the documentation, the "name" parameter seems to refer to > > an existing database FK constraint rather than specifying the name of > > the generated constraint. > > > (My problem is that I am migrating from SQLite to Oracle and its 30 > > char limit of identifiers is causing problems with Foreign key > > constraint names). > > "name" on ForeignKeyConstraint is the name that would be placed within > the "CONSTRAINT <name> FOREIGN KEY" clause of the generated DDL. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
