summaryrefslogtreecommitdiff
path: root/test
Commit message (Collapse)AuthorAgeFilesLines
* not fails_if cymysqlHajime Nakagami2013-07-141-1/+1
|
* remove skip decorator for mysql+cymysqlHajime Nakagami2013-07-131-1/+0
|
* @testing.crashes('mysql+cymysql', 'blocking')Hajime Nakagami2013-07-131-1/+2
|
* Fixed bug where the expression system relied upon the ``str()``Mike Bayer2013-07-122-0/+53
| | | | | | | | | | | | 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]
* Dialect.initialize() is not called a second time if an :class:`.Engine`Mike Bayer2013-07-111-3/+31
| | | | | | 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-091-0/+2
| | | | | has_table issues are OK. On OSX forget it. - still some issues with PY3k + pyodbc + decimal values it doesn't expect, not sure
* callcountsMike Bayer2013-07-081-32/+32
|
* - create a new system where we can decorate an event methodMike Bayer2013-07-082-21/+287
| | | | | | | | | | | | | | | | 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]
* - Added new method to the :func:`.insert` constructMike Bayer2013-07-052-2/+134
| | | | | | | | | | :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.
* Fixed bug whereby attribute history functions would failMike Bayer2013-07-041-43/+128
| | | | | | | 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-041-1/+50
| | | | | | checked out count if an existing pooled connection failed to reconnect after an invalidate or recycle event. Also in 0.8.3. [ticket:2772]
* 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-021-0/+3
|
* Fixed bug when using multi-table UPDATE where a supplementalMike Bayer2013-07-021-0/+39
| | | | | | | 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-021-1/+3
| | | | | reflected by the SQLite dialect; courtesy Russell Stuart. [ticket:2764]
* ORM descriptors such as hybrid properties can now be referencedMike Bayer2013-07-021-2/+37
| | | | | | 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
|
* - refactor pool a bit so that intent between ↵Mike Bayer2013-07-024-83/+164
| | | | | | | | | | | | | | 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
* Added new flag ``retaining=False`` to the kinterbasdb and fdb dialects.Mike Bayer2013-06-301-0/+73
| | | | | | | 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-309-493/+456
| | | | | | | | | | | | 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-301-2/+33
| | | | 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-301-3/+23
| | | | | 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-282-56/+161
| | | | | | | | | 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
|
* Fixed bug in HSTORE type where keys/values that containedMike Bayer2013-06-281-0/+37
| | | | | | | 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-272-0/+89
| | | | | adapter to an aliased-mapped, non-polymorphic selectable that prevented us from referring directly to that selectable.
* add an ORDER BY hereMike Bayer2013-06-261-2/+2
|
* - rework of correlation, continuing on #2668, #2746Mike Bayer2013-06-263-38/+210
| | | | | | | | | | | | | | | | | | | | | | | | - add support for correlations to propagate all the way in; because correlations require context now, need to make sure a select enclosure of any level takes effect any number of levels deep. - fix what we said correlate_except() was supposed to do when we first released #2668 - "the FROM clause is left intact if the correlated SELECT is not used in the context of an enclosing SELECT..." - it was not considering the "existing_froms" collection at all, and prohibited additional FROMs from being placed in an any() or has(). - add test for multilevel any() - lots of docs, including glossary entries as we really need to define "WHERE clause", "columns clause" etc. so that we can explain correlation better - based on the insight that a SELECT can correlate anything that ultimately came from an enclosing SELECT that links to this one via WHERE/columns/HAVING/ORDER BY, have the compiler keep track of the FROM lists that correspond in this way, link it to the asfrom flag, so that we send to _get_display_froms() the exact list of candidate FROMs to correlate. no longer need any asfrom logic in the Select() itself - preserve 0.8.1's behavior for correlation when no correlate options are given, not to mention 0.7 and prior's behavior of not propagating implicit correlation more than one level.. this is to reduce surprises/hard-to-debug situations when a user isn't trying to correlate anything.
* YEAR(2) emits a warning and oursql / mysqlconnector throw an exceptionMike Bayer2013-06-231-4/+2
| | | | on the warning so just dump it
* - add a test for pullreq 8Mike Bayer2013-06-231-0/+26
| | | | - simplify
* tweak this for now, would need a testMike Bayer2013-06-231-11/+0
|
* The resolution of :class:`.ForeignKey` objects to theirMike Bayer2013-06-233-36/+323
| | | | | | | | | | | | | | | | | | target :class:`.Column` has been reworked to be as immediate as possible, based on the moment that the target :class:`.Column` is associated with the same :class:`.MetaData` as this :class:`.ForeignKey`, rather than waiting for the first time a join is constructed, or similar. This along with other improvements allows earlier detection of some foreign key configuration issues. Also included here is a rework of the type-propagation system, so that it should be reliable now to set the type as ``None`` on any :class:`.Column` that refers to another via :class:`.ForeignKey` - the type will be copied from the target column as soon as that other column is associated, and now works for composite foreign keys as well. [ticket:1765]
* Fix unicode literals on Python 3.1 and 3.2pr/10Roman Podolyaka2013-06-231-8/+8
| | | | | A few tests use u'' unicode literals which are not supported in Python versions 3.1 and 3.2.
* Provided a new attribute for :class:`.TypeDecorator`Mike Bayer2013-06-221-1/+33
| | | | | | | | | called :attr:`.TypeDecorator.coerce_to_is_types`, to make it easier to control how comparisons using ``==`` or ``!=`` to ``None`` and boolean types goes about producing an ``IS`` expression, or a plain equality expression with a bound parameter. [ticket:2744]
* this locale is not needed. maybe it is somewhere but the locale I have ↵Mike Bayer2013-06-222-18/+9
| | | | | | ("C", whatever that means, cannot find meaning of this anywhere in Postgresql documentation) seems to work
* Merge pull request #5 from cjw296/pg-rangesmike bayer2013-06-222-1/+344
|\ | | | | Support for Postgres range types.
| * Implement EXCLUDE constraints for postgres.Chris Withers2013-06-101-1/+49
| |
| * add support for range operators listed in ↵Chris Withers2013-06-101-1/+159
| | | | | | | | http://www.postgresql.org/docs/9.2/interactive/functions-range.html
| * Basic type support for the new range types in postgres 9.2Chris Withers2013-06-102-1/+138
| |
* | turn this requirement back down as the simpler serialize works better nowMike Bayer2013-06-172-8/+1
| |
* | - rework PropComparator.adapted() to be PropComparator.adapt_to_entity(),Mike Bayer2013-06-171-1/+1
| | | | | | | | | | | | | | passes in AliasedInsp and allows more flexibility. - rework the AliasedClass/AliasedInsp relationship so that AliasedInsp has all state and functionality. AliasedClass is just a facade. [ticket:2756]
* | can remove this, issue is fixedMike Bayer2013-06-171-10/+1
| |
* | - clean up this test (really we don't even need this, it's not testing much)Mike Bayer2013-06-161-13/+20
| | | | | | | | | | - for the moment, put a catch in it to see if we can trap that issue on jenkins
* | Merge pull request #7 from malor/psycopg2_execution_optionsmike bayer2013-06-151-0/+10
|\ \ | | | | | | Add AUTOCOMMIT isolation level support for psycopg2
| * | Add AUTOCOMMIT isolation level support for psycopg2pr/7Roman Podolyaka2013-06-151-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | One can use this to emit statements, which can not be executed within a transaction (e. g. CREATE DATABASE): from sqlalchemy import create_engine eng = create_engine('postgresql://test:test@localhost/test') conn = eng.connect().execution_options(isolation_level='AUTOCOMMIT') conn.execute('CREATE DATABASE test2;') Fixes issue #2072.
View Lorry Controller Status