Re: [Sqlalchemy-tickets] [sqlalchemy] #2913: Table.tometadata() foreign key copying behavior with different schemas

[sqlalchemy <mi...@zz...>]

#2913: Table.tometadata() foreign key copying behavior with different schemas
-----------------------------------+-------------------------------
      Reporter:  dtheodor          |      Owner:  zzzeek
          Type:  defect            |     Status:  closed
      Priority:  high              |  Milestone:  0.9.2
     Component:  schema            |   Severity:  major - 1-3 hours
    Resolution:  fixed             |   Keywords:  tometadata
Progress State:  completed/closed  |
-----------------------------------+-------------------------------
Changes (by zzzeek):

 * status:  new => closed
 * resolution:   => fixed
 * status_field:  in queue => completed/closed


Comment:

 both of these changes have been made in r2d4b457924fa722ef2cf.  this
 includes the FK schema change based on the referenced schema being the
 same as the parent schema, as well as a new optional callable
 `referred_schema_fn` which can be provided to supply any kind of logic to
 how the referenced schemas should be assigned.

--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2913#comment:4>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python