On 9/13/07, Rick Morrison <[EMAIL PROTECTED]> wrote: > SA 0.3* doesn't seem to handle relationships between tables in different > schemas very well: it seems to think that > > schema.A -> public.B > > is: > > schema.A -> schema.B > > and even specifying "primaryjoin=" in the mapper won't help it. There seems > to be no directive to say "use the default / primary schema" > > (I'm using MSSQL, but I've seen very similar q's regarding both PG and > Oracle, so I suspect it's not a db-specific issue) > > > Just curious if there's been any work in this area on 0.4 in this area? I've > been avoiding jumping in to 0.4 so far, but this could be the issue that > gives me the push.
I'm not sure about creation, but I've not had any problems using cross-schema foreign keys, relations, joins and so forth using SQLAlchemy 0.3 and PostgreSQL. We're using Elixir (and I had to fix a bug in Elixir's relation management for it to pass things through to SQLAlchemy properly). Neil -- Neil Blakey-Milner http://nxsy.org/ [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
