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

 {{{
 Postgresql *does not tell us the schema of the constraint* if that schema
 is in the search path.
 }}}

 Ok, this is clear! As you said "game over". I could try to look around if
 I can find some mean to circumvent this limitation, but it would be a bit
 presomptuous of me to think that I can find a way where you didn't :).

 Would it be possible that backup/change/introspect/restore search_path
 could solve this issue? (maybe it would break many, many other things?)


 Anyway, thanks for digging into this "non issue". I will probably just
 redefine search_path at connection level. Maybe this ticket will be useful
 for other people that hit similar search_path problems (I've seen report
 like this one on debian mailing-list that were left unanswered).

 To conclude, many many thanks for the great job you're doing on
 SqlAlchemy.

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