| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
a dotted schema.tablename combination, if the foreign key
references a table in a remote schema. [ticket:1405]
|
| |
|
| |
|
| |
|
|
|
|
| |
schema. unit test TBD.
|
|
|
|
|
|
|
| |
to "%%".
Because of the backwards incompatible nature of this change,
a warning is emitted if '%%' is detected in the string. [ticket:1267]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
during reflection. [ticket:1241]
|
|
|
|
| |
with a more succinct "dialect.execution_ctx_cls" member
|
|
|
|
|
|
|
|
| |
testing issues,
and also addresses a significant chunk of py3k deprecations. It's mainly
expicit __hash__ methods. Additionally, most usage of sets/dicts to store columns uses
util-based placeholder names.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
a private method. Subclassing Connection
is not needed now that ConnectionProxy
is available.
- tightened the interface for the various _execute_XXX()
methods to reduce ambiguity
- __distill_params() no longer creates artificial [{}] entry,
blank dict is no longer passed through to do_execute()
in any case unless explicitly sent from the outside
as in connection.execute("somestring"), {})
- fixed a few old sql.query tests which were doing that
- removed needless do_execute() from mysql dialect
- fixed charset param not properly being sent to
_compat_fetchone() in mysql
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Documentation has been converted to Sphinx.
In particular, the generated API documentation
has been constructed into a full blown
"API Reference" section which organizes
editorial documentation combined with
generated docstrings. Cross linking between
sections and API docs are vastly improved,
a javascript-powered search feature is
provided, and a full index of all
classes, functions and members is provided.
|
|
|
|
|
|
| |
to be based solely on presence of cursor.description.
All the regexp-based guessing about statements returning rows
has been removed [ticket:1212].
|
|
|
|
| |
issue will be addressed more fully by [ticket:1212].
|
| |
|
|
|
|
| |
#1206.
|
|
|
|
| |
provided a schema= that matches the connection's default schema.
|
| |
|
|
|
|
|
| |
the parenthesis, which seem to get in the way when using in
conjunction with executemany().
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
of work logging is now
class level like all the other logging.
- trimmed back the logging API, centralized class_logger() as the single point of configuration for
logging, removed per-instance logging checks from ORM.
- Engine and Pool logging remain at the instance level. The modulus of "instance ids" has been upped
to 65535. I'd like to remove the modulus altogether but I do see a couple of users each month
calling create_engine() on a per-request basis, an incorrect practice but I'd rather their applications
don't just run out of memory.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to 'scale'. 'length' is deprecated and is still accepted
with a warning. [ticket:827]
- The 'length' argument to MSInteger, MSBigInteger, MSTinyInteger,
MSSmallInteger and MSYear has been renamed to 'display_width'.
[ticket:827]
- mysql._Numeric now consumes 'unsigned' and 'zerofill' from
the given kw, so that the same kw can be passed along to Numeric
and allow the 'length' deprecation logic to still take effect
- added testlib.engines.all_dialects() to return a dialect for
every db module
- informix added to sqlalchemy.databases.__all__. Since other
"experimental" dbs like access and sybase are there, informix
should be as well.
|
|
|
|
|
| |
The change is backward compatible. Slight expansion of patch from catlee.
Thanks! [ticket:1110]
|
| |
|
| |
|
|
|
|
| |
(sets.Set-based collections & DB-API returns still work.)
|
|
|
|
| |
on PostgreSQL, SQLite, MySQL, MS-SQL, and Oracle backends.
|
|
|
|
|
| |
- removed ancient descriptor() functions from dialects; replaced with Dialect.name
- removed similarly ancient sys.modules silliness in Engine.name
|
| |
|
|
|
|
| |
- NameError doesn't have "message" in py2.4
|
| |
|
|
|
|
| |
(this actually allows CAST (foo, VARCHAR) to render too)
|
|
|
|
| |
0.4 development continues at /sqlalchemy/branches/rel_0_4
|
| |
|
|
|
|
|
| |
- MySQL character set caching is more aggressive but will invalidate the cache if a SET is issued.
- MySQL connection memos are namespaced: info[('mysql', 'server_variable')]
|
|
|
|
|
|
| |
test results showing tuples faster
- changed cache decorator call on default_schema_name call to a connection.info specific one
|
| |
|
| |
|
| |
|
|
|
|
| |
- Deprecation decorator is now a real decorator
|
| |
|
|
|
|
|
|
|
| |
The dialect needs a hook run on first pool connect to detect this most of
the time, and a refactor with Dialect-per-Connection to get it right all of
the time. (It's a connection-session scoped setting with dialect-modifying
behavior)
|
| |
|
|
|
|
|
|
| |
util.warn() wraps this up.
- SADeprecationWarning has moved to exceptions. An alias remains in logging until 0.5.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
deprecated until 0.5. The "upgrading" behavior of String to Text
when no length is present is also deprecated until 0.5; will issue a
warning when used for CREATE TABLE statements (String with no length
for SQL expression purposes is still fine) [ticket:912]
|
| |
|