Having to support different PostgreSQL schemas per web request and finding my current approach of setting the PostgreSQL schema search path a bit convoluted, when I try to use longer lived sessions in unit tests for convenience, because the session starts using a new database connection after a commit, I came across 'sqlalchemy.schema.ThreadLocalMetaData' which would seem to be an elegant solution for the problem if it supported a different 'schema' per thread as it does a different 'bind'.
My question is: would it be feasible and does it make sense to 'schema' support to 'sqlalchemy.schema.ThreadLocalMetaData' for cases such as the one I described above? Thanks in advance for any feedback on this. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
