summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* set cymysql's supports_unicode_statements=True for python3pr/16Hajime Nakagami2013-07-161-0/+1
|
* fix compat.iterbytes importHajime Nakagami2013-07-142-2/+2
|
* not fails_if cymysqlHajime Nakagami2013-07-141-1/+1
|
* use map() instead of util.iterbytes()Hajime Nakagami2013-07-141-1/+1
|
* not supports_sane_multi_rowcount in cymysqlHajime Nakagami2013-07-141-0/+1
|
* remove skip decorator for mysql+cymysqlHajime Nakagami2013-07-131-1/+0
|
* mysql+cython supports_sane_rowcount = TrueHajime Nakagami2013-07-131-1/+1
|
* @testing.crashes('mysql+cymysql', 'blocking')Hajime Nakagami2013-07-131-1/+2
|
* - use inline=True for the insert..select here so it works on oracleMike Bayer2013-07-122-2/+13
|
* CSS tweaks to support version styling in the latest versions of sphinxMike Bayer2013-07-121-9/+16
|
* Fixed bug where the expression system relied upon the ``str()``Mike Bayer2013-07-128-5/+118
| | | | | | | | | | | | form of a some expressions when referring to the ``.c`` collection on a ``select()`` construct, but the ``str()`` form isn't available since the element relies on dialect-specific compilation constructs, notably the ``__getitem__()`` operator as used with a Postgresql ``ARRAY`` element. The fix also adds a new exception class :class:`.UnsupportedCompilationError` which is raised in those cases where a compiler is asked to compile something it doesn't know how to. Also in 0.8.3. [ticket:2780]
* don't split the regexps for chop_traceback()Mike Bayer2013-07-121-4/+2
|
* Dialect.initialize() is not called a second time if an :class:`.Engine`Mike Bayer2013-07-116-4/+63
| | | | | | is recreated, due to a disconnect error. This fixes a particular issue in the Oracle 8 dialect, but in general the dialect.initialize() phase should only be once per dialect. Also in 0.8.3. [ticket:2776]
* - we dont actually need this unicode cast, on py3k + linux it seems theMike Bayer2013-07-093-8/+4
| | | | | has_table issues are OK. On OSX forget it. - still some issues with PY3k + pyodbc + decimal values it doesn't expect, not sure
* changelog for 2355Mike Bayer2013-07-091-0/+7
|
* callcountsMike Bayer2013-07-081-32/+32
|
* - create a new system where we can decorate an event methodMike Bayer2013-07-0812-78/+668
| | | | | | | | | | | | | | | | with @_legacy_signature, will inspect incoming listener functions to see if they match an older signature, will wrap into a newer sig - add an event listen argument named=True, will send all args as kw args so that event listeners can be written with **kw, any combination of names - add a doc system to events that writes out the various calling styles for a given event, produces deprecation messages automatically. a little concerned that it's a bit verbose but will look at it up on RTD for awhile to get a feel. - change the calling signature for bulk update/delete events - we have the BulkUD object right there, and there's at least six or seven things people might want to see, so just send the whole BulkUD in [ticket:2775]
* remove undoc-members from query docstring [ticket:2774]Mike Bayer2013-07-072-1/+7
|
* use "target tables" hereMike Bayer2013-07-062-2/+2
|
* - Added new method to the :func:`.insert` constructMike Bayer2013-07-0510-5/+315
| | | | | | | | | | :meth:`.Insert.from_select`. Given a list of columns and a selectable, renders ``INSERT INTO (table) (columns) SELECT ..``. While this feature is highlighted as part of 0.9 it is also backported to 0.8.3. [ticket:722] - The :func:`.update`, :func:`.insert`, and :func:`.delete` constructs will now interpret ORM entities as FROM clauses to be operated upon, in the same way that select() already does. Also in 0.8.3.
* 0.9 changelogMike Bayer2013-07-041-0/+9
|
* Fixed bug whereby attribute history functions would failMike Bayer2013-07-043-45/+139
| | | | | | | when an object we moved from "persistent" to "pending" using the :func:`.make_transient` function, for operations involving collection-based backrefs. [ticket:2773]
* Fixed bug where :class:`.QueuePool` would lose the correctMike Bayer2013-07-044-2/+75
| | | | | | checked out count if an existing pooled connection failed to reconnect after an invalidate or recycle event. Also in 0.8.3. [ticket:2772]
* 0.8.2Mike Bayer2013-07-031-0/+1
|
* dont need thisMike Bayer2013-07-031-1/+1
|
* make this rule automatic based on coverage pluginMike Bayer2013-07-031-5/+8
|
* for this test, apparently we don't handle sets as unordered since neither doesMike Bayer2013-07-021-3/+9
| | | | | MySQL. for some reason set ordering was constant when testing mysqldb, but not so with oursql.
* add a float exclusion to help oursql build 100%Mike Bayer2013-07-023-0/+13
|
* Fixed bug when using multi-table UPDATE where a supplementalMike Bayer2013-07-024-2/+59
| | | | | | | table is a SELECT with its own bound parameters, where the positioning of the bound parameters would be reversed versus the statement itself when using MySQL's special syntax. [ticket:2768]
* Added :class:`.BIGINT` to the list of type names that can beMike Bayer2013-07-024-3/+22
| | | | | reflected by the SQLite dialect; courtesy Russell Stuart. [ticket:2764]
* ORM descriptors such as hybrid properties can now be referencedMike Bayer2013-07-024-12/+67
| | | | | | by name in a string argument used with ``order_by``, ``primaryjoin``, or similar in :func:`.relationship`, in addition to column-bound attributes. [ticket:2761]
* profile tweakMike Bayer2013-07-021-9/+8
|
* see alsoMike Bayer2013-07-022-0/+12
|
* - distribute/setuptools all over the place right nowMike Bayer2013-07-022-799/+0
|
* - refactor pool a bit so that intent between ↵Mike Bayer2013-07-0210-193/+419
| | | | | | | | | | | | | | ConnectionRecord/ConnectionFairy is clear; make sure that the DBAPI connection passed to the reset-on-return events/dialect hooks is also a "fairy", so that dictionaries like "info" are available. [ticket:2770] - rework the execution_options system so that the dialect is given the job of making any immediate adjustments based on a set event. move the "isolation level" logic to use this new system. Also work things out so that even engine-level execution options can be used for things like isolation level; the dialect attaches a connect-event handler in this case to handle the task. - to support this new system as well as further extensibiltiy of execution options add events engine_connect(), set_connection_execution_options(), set_engine_execution_options()
* mark the tests that seem to be segfauling py3k+coverage so that we can ↵Mike Bayer2013-06-302-0/+16
| | | | | | exclude them at the nose command line
* fix syntax screwupMike Bayer2013-06-302-0/+2
|
* Added new flag ``retaining=False`` to the kinterbasdb and fdb dialects.Mike Bayer2013-06-307-46/+208
| | | | | | | This controls the value of the ``retaining`` flag sent to the ``commit()`` and ``rollback()`` methods of the DBAPI connection. Defaults to False. Also in 0.8.2, where it defaults to True. [ticket:2763]
* - replace most explicitly-named test objects called "Mock..." withMike Bayer2013-06-3017-497/+502
| | | | | | | | | | | | actual mock objects from the mock library. I'd like to use mock for new tests so we might as well use it in obvious places. - use unittest.mock in py3.3 - changelog - add a note to README.unittests - add tests_require in setup.py - have tests import from sqlalchemy.testing.mock - apply usage of mock to one of the event tests. we can be using this approach all over the place.
* - additional fix for [ticket:2750] where on an update, we make sure theMike Bayer2013-06-302-3/+35
| | | | value is present
* add better tests for [ticket:2750]Mike Bayer2013-06-301-3/+45
|
* A warning is emitted when trying to flush an object of an inheritedMike Bayer2013-06-305-4/+74
| | | | | mapped class where the polymorphic discriminator has been assigned to a value that is invalid for the class. [ticket:2750]
* tweak the timings here to maximize chance of test successMike Bayer2013-06-291-31/+12
|
* set UTC timezone on the connection here so we can get consistent resultsMike Bayer2013-06-291-6/+9
|
* The behavior of :func:`.extract` has been simplified on theMike Bayer2013-06-285-78/+184
| | | | | | | | | Postgresql dialect to no longer inject a hardcoded ``::timestamp`` or similar cast into the given expression, as this interfered with types such as timezone-aware datetimes, but also does not appear to be at all necessary with modern versions of psycopg2. Also in 0.8.2. [ticket:2740]
* refactor test suites for postgresql, mssql, mysql into packages.Mike Bayer2013-06-2821-7350/+7449
|
* improve the close handling here so that we don't double-close a connection;Mike Bayer2013-06-281-3/+5
| | | | we log this now so it apparently happens a bunch
* Type lookup when reflecting the Firebird types LONG andMike Bayer2013-06-283-7/+26
| | | | | | | | INT64 has been fixed so that LONG is treated as INTEGER, INT64 treated as BIGINT, unless the type has a "precision" in which case it's treated as NUMERIC. Patch courtesy Russell Stuart. [ticket:2757]
* Fixed bug in HSTORE type where keys/values that containedMike Bayer2013-06-284-3/+59
| | | | | | | backslashed quotes would not be escaped correctly when using the "non native" (i.e. non-psycopg2) means of translating HSTORE data. Patch courtesy Ryan Kelly. [ticket:2766]
* - fix a regression caused by #2587, where query.join() would apply anMike Bayer2013-06-273-1/+90
| | | | | adapter to an aliased-mapped, non-polymorphic selectable that prevented us from referring directly to that selectable.
View Lorry Controller Status