phrrn...@googlemail.com wrote:
>
> Sybase (and SQL Server) support cross-database JOINs (Sybase even
> supports cross-database foreign-key constraints). There are four
> components to an object identifier:
>
> 1 = Object name
> 2 = Schema name
> 3 = Database name
> 4 = Server name
>
> the dataserver, database and schema are assumed for one-part
> identifiers (e.g. 'foo'), dataserver and database assumed for two-part
> identifiers (e.g. 'dbo.foo') and, finally, dataserver assumed for
> three-part identifiers ('production.dbo.foo')
>
> e.g. SELECT foo.* FROM BANANA.production.dbo.foo
> SELECT foo.* FROM production.dbo.foo
> SELECT foo.* FROM production..foo -- same as the previous query
> if the callers default schema is dbo
> SELECT foo.* FROM dbo.foo
> SELECT foo.* FROM foo
> SELECT foo.* FROM ..foo
> I am not so interested in supporting four-part identifiers in SA but I
> would like to figure out how to support three-part identifiers as very
> many of our databases have cross-database references.
>
> One natural (to me!) way of doing this is to add a 'database' property
> to the Table and ForeignKeyConstraint schema items and have the Sybase/
> SQL Server dialects always emit fully-qualified three-part identifiers
> for table names.
we have an element on Table called "schema". I had in mind that schema
should accept dotted names, so SQLA generally doesn't need to get
involved. The only change needed is to the IdentifierPreparer, such that
when quote_schema is called, it separates the name along the dot first so
that it can quote each token separately.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to
sqlalchemy+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---
