Re: [Sqlalchemy-tickets] [sqlalchemy] #2922: Metadata.reflect failed on different schema foreign key constraint (postgresql)

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

#2922: Metadata.reflect failed on different schema foreign key constraint
(postgresql)
-------------------------------------------+-------------------------------
      Reporter:  vrobin                    |      Owner:  zzzeek
          Type:  defect                    |     Status:  new
      Priority:  medium                    |  Milestone:
     Component:  postgres                  |   Severity:  no triage
    Resolution:                            |  selected yet
Progress State:  needs questions answered  |   Keywords:
-------------------------------------------+-------------------------------

Comment (by zzzeek):

 looking more closely, it seems like the issue is not as much that we don't
 know the schema, as it is actually in both results, but that we don't know
 how to interpret this schema compared to how the user has set up the Table
 defs.   That is, someone might have schema A, B, C in their search path,
 and they want to use `Table` in a schemaless fashion across all three.  So
 when we reflect a constraint from A to B, we want the correct "B" Table -
 e.g. the one with or without the schema.

 So i think the issue is more like we had to make a choice how to appease
 people using table reflection in different ways with different search
 paths.

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