]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
- Reflected foreign keys will properly locate
authorMike Bayer <mike_mp@zzzcomputing.com>
Fri, 26 Dec 2008 05:28:38 +0000 (05:28 +0000)
committerMike Bayer <mike_mp@zzzcomputing.com>
Fri, 26 Dec 2008 05:28:38 +0000 (05:28 +0000)
commit83a756c5415fad752933ed7f1aff69d2a184d618
tree679b6d9ef7f383fc1c82fa4f27cc7591f015c116
parent3ea2888b7f84ef7571c847991149c7372dd3db49
- Reflected foreign keys will properly locate
their referenced column, even if the column
was given a "key" attribute different from
the reflected name.  This is achieved via a
new flag on ForeignKey/ForeignKeyConstraint
called "link_to_name", if True means the given
name is the referred-to column's name, not its
assigned key.
[ticket:650]
- removed column types from sqlite doc, we
aren't going to list out "implementation" types
since they aren't significant and are less present
in 0.6
- mysql will report on missing reflected foreign
key targets in the same way as other dialects
(we can improve that to be immediate within
reflecttable(), but it should be within
ForeignKeyConstraint()).
- postgres dialect can reflect table with
an include_columns list that doesn't include
one or more primary key columns
14 files changed:
CHANGES
doc/build/reference/dialects/sqlite.rst
lib/sqlalchemy/databases/access.py
lib/sqlalchemy/databases/firebird.py
lib/sqlalchemy/databases/informix.py
lib/sqlalchemy/databases/maxdb.py
lib/sqlalchemy/databases/mssql.py
lib/sqlalchemy/databases/mysql.py
lib/sqlalchemy/databases/oracle.py
lib/sqlalchemy/databases/postgres.py
lib/sqlalchemy/databases/sqlite.py
lib/sqlalchemy/databases/sybase.py
lib/sqlalchemy/schema.py
test/engine/reflection.py