| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
|
|
|
| |
- 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.
|
|
|
|
|
|
| |
two-phase commit. We now have field reports
of Oracle two-phase commit working properly
with this change.
|
|
|
|
|
| |
- Calling alias.execute() in conjunction with
server_side_cursors won't raise AttributeError.
|
|
|
|
| |
to appropriately flag it as not supported on mssql. I sure hope I didn't jack things up for other dialects. Cleaned up a comment and removed some commented pdb statements.
|
|
|
|
| |
correctly adjusts the CAST accordingly.
|
| |
|
|
|
|
| |
columns. Fixes #973.
|
|
|
|
| |
use the correct host,port syntax, otherwise use the Port= parameter in the connection string. Fixes #1192.
|
|
|
|
| |
mssql.
|
| |
|
|
|
|
| |
column.foreign_key property.
|
| |
|
|
|
|
| |
to missing Currency type. Functions didn't return the value. JOINS must be specified as LEFT OUTER JOIN or INNER JOIN. Fixes #1017.
|
|
|
|
| |
#1217.
|
| |
|
|
|
|
| |
the IN / NOT IN syntax when using a binary expression with a subquery.
|
| |
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
[ticket:1178]
|
|
|
|
|
| |
- wrote a docstring for oracle dialect, needs formatting perhaps
- made FIRST_ROWS optimization optional based on optimize_limits=True, [ticket:536]
|
|
|
|
| |
sides.
|
|
|
|
| |
insert. If supports_empty_insert is True then the backend specifically supports the 'insert into t1 () values ()' syntax. If supports_default_values is True then the backend supports the 'insert into t1 default values' syntax. If both are false then the backend has no support for empty inserts at all and an exception gets raised. Changes here are careful to not change current behavior except where the current behavior was failing to begin with.
|
|
|
|
| |
keys. Fixes 1193. Added server version info into mssql pyodbc dialect.
|
|
|
|
|
|
|
|
|
|
|
|
| |
- The internal notion of an "OID" or "ROWID" column has been
removed. It's basically not used by any dialect, and the
possibility of its usage with psycopg2's cursor.lastrowid
is basically gone now that INSERT..RETURNING is available.
- Removed "default_order_by()" method on all FromClause
objects.
- profile/compile/select test is 8 function calls over on buildbot 2.4 for some reason, will adjust after checking
the results of this commit
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to an instance will not drop into an EXISTS clause
and will compare foreign key columns instead.
- removed not-really-working use cases of comparing
a collection to an iterable. Use contains() to test
for collection membership.
- Further simplified SELECT compilation and its relationship
to result row processing.
- Direct execution of a union() construct will properly set up
result-row processing. [ticket:1194]
|
|
|
|
|
|
|
| |
logic disabled in the sqlite dialect, to adjust for pysqlite
2.5.0's new requirement that only Python unicode objects are
accepted;
http://itsystementwicklung.de/pipermail/list-pysqlite/2008-March/000018.html
|
|
|
|
| |
function overrides. Fixed up the test_select in the sql/defaults.py tests which was a mess.
|
|
|
|
| |
the assumed default is dbo, whereas it could be modified by the connection. Allows SchemaTest.test_select to pass now.
|
|
|
|
|
| |
comments at the front before a SELECT as SELECT statements.
[ticket:1187]
|
| |
|
|
|
|
| |
a little more
|
|
|
|
|
|
| |
to use regular expressions and format strings, rather
than strptime/strftime, to generically support
pre-1900 dates, dates with microseconds. [ticket:968]
|
|
|
|
|
| |
the parenthesis, which seem to get in the way when using in
conjunction with executemany().
|
| |
|
| |
|
|
|
|
| |
account [ticket:1155]
|
|
|
|
|
|
| |
and instead uses subqueries in conjunction with a special
Oracle optimization comment. Allows LIMIT/OFFSET to work
in conjunction with DISTINCT. [ticket:536]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
from [ticket:1068]. This feature is on hold
pending further development.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
own name
and not its contained expression, if the dialect reports true for supports_simple_order_by_label.
the flag is not propagated forwards, meant to closely mimic the syntax Postgres expects which is
that only a simple name can be in the ORDER BY, not a more complex expression or function call
with the label name embedded (mysql and sqlite support more complex expressions).
This further sets the standard for propigation of **kwargs within compiler, that we can't just send
**kwargs along blindly to each XXX.process() call; whenever a **kwarg needs to propagate through,
most methods will have to be aware of it and know when they should send it on forward and when not.
This was actually already the case with result_map as well.
The supports_simple_order_by dialect flag defaults to True but is conservatively explicitly set to
False on all dialects except SQLite/MySQL/Postgres to start.
[ticket:1068]
|
| |
|
|
|
|
| |
Addresses #909 in a purposeful way.
|
|
|
|
| |
reflecttable for reflecting the mssql tables. Removed unicode reflection test from mssql. Need to investigate this further.
|
|
|
|
|
| |
The change is backward compatible. Slight expansion of patch from catlee.
Thanks! [ticket:1110]
|