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):

 Replying to [comment:4 vrobin]:
 > There may be an intrinsic problem with this use of explicit schema (in
 DDL, in SQLAlchemy reflection) along with an implicit schema resolution
 (specific search_path) which is set at the db level, but I fail to see it.

 there is, and it is exactly what is being referred to in the document I
 linked:  http://docs.sqlalchemy.org/en/rel_0_9/dialects/postgresql.html
 #remote-cross-schema-table-introspection

 Postgresql *does not tell us the schema of the constraint* if that schema
 is in the search path.   E.g., a particular query that normally tells us
 "refers to someotherschema.sometable.somecolumn" now tells us only
 "sometable.somecolumn".  That's it, game over, we are not told what the
 schema name is.    A lot of work went into figuring this out.  I'll go
 over your test later but pretty much this issue is a "wontfix".

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