summaryrefslogtreecommitdiff
path: root/test/sql/test_defaults.py
Commit message (Collapse)AuthorAgeFilesLines
...
* tests for FK/autoincrement selectionMike Bayer2011-12-061-0/+24
|
* - Fixed bug where "autoincrement" detection onMike Bayer2011-06-301-1/+11
| | | | | | | Table would fail if the type had no "affinity" value, in particular this would occur when using the UUID example on the site that uses TypeEngine as the "impl".
* fix some testsMike Bayer2011-06-021-1/+1
|
* - move all the comments that got shoved below the fixture grabs back upMike Bayer2011-03-271-0/+4
|
* - remove test.sql._base, test.engine._base, test.orm._base, move those ↵Mike Bayer2011-03-271-13/+13
| | | | | | | classes to a new test.lib.fixtures module - move testing.TestBase to test.lib.fixtures - massive search and replace
* - convert @provide_metadata to use self accessMike Bayer2011-03-261-0/+12
| | | | | - having occasional issues with BasicEntity grabbing, if it persists may have to pass an explicit base class into setup_classes()/setup_mappers()
* - remove @testing.resolve_artifact_names, replace with direct attributeMike Bayer2011-03-261-4/+4
| | | | | | | access to the cls/self.tables/classes registries - express orm/_base.py ORMTest in terms of engine/_base.py TablesTest, factor out common steps into TablesTest, remove AltEngineTest as a separate class. will further consolidate these base classes
* - Added new generic function "next_value()", acceptsMike Bayer2011-03-201-26/+184
| | | | | | | | | | | | | | | | | | | | a Sequence object as its argument and renders the appropriate "next value" generation string on the target platform, if supported. Also provides ".next_value()" method on Sequence itself. [ticket:2085] - added tests for all the conditions described in [ticket:2085] - postgresql dialect will exec/compile a Sequence that has "optional=True". the optional flag is now only checked specifically in the context of a Table primary key evaulation. - func.next_value() or other SQL expression can be embedded directly into an insert() construct, and if implicit or explicit "returning" is used in conjunction with a primary key column, the newly generated value will be present in result.inserted_primary_key. [ticket:2084]
* Tests for unicode columns with non-unicode defaults. See #2079.Taavi Burns2011-03-141-1/+27
|
* - The Sequence() construct, when passed a MetaData()Mike Bayer2011-02-131-84/+124
| | | | | | | object via its 'metadata' argument, will be included in CREATE/DROP statements within metadata.create_all() and metadata.drop_all(), including "checkfirst" logic. [ticket:2055]
* - Non-DBAPI errors which occur in the scope of an `execute()`Mike Bayer2011-02-091-2/+2
| | | | | | | | call are now wrapped in sqlalchemy.exc.StatementError, and the text of the SQL statement and repr() of params is included. This makes it easier to identify statement executions which fail before the DBAPI becomes involved. [ticket:2015]
* Regarding reflection for this case, reflection of an int PK colMike Bayer2011-01-151-5/+0
| | | | | | with a server_default sets the "autoincrement" flag to False, except in the case of a PG SERIAL col where we detected a sequence default. [ticket:2020] [ticket:2021]
* - getting slightly more consistent behavior for the edge case of pk columnsMike Bayer2011-01-151-7/+138
| | | | | | with server default - autoincrement is now false with any server_default, so these all return None, applies consistency to [ticket:2020], [ticket:2021]. if prefetch is desired a "default" should be used instead of server_default.
* - dont count server_default absense as part of autoincrement, PGMike Bayer2011-01-121-1/+0
| | | | | | will have a value here upon reflection. - mysql, others will have to check "server_default" when rendering special keywords like AUTOINCREMENT
* - A TypeDecorator of Integer can be used with a primary keyMike Bayer2011-01-111-3/+82
| | | | | | | | | | | | | | | | | | | column, and the "autoincrement" feature of various dialects as well as the "sqlite_autoincrement" flag will honor the underlying database type as being Integer-based. [ticket:2005] - Result-row processors are applied to pre-executed SQL defaults, as well as cursor.lastrowid, when determining the contents of result.inserted_primary_key. [ticket:2006] - Bind parameters present in the "columns clause" of a select are now auto-labeled like other "anonymous" clauses, which among other things allows their "type" to be meaningful when the row is fetched, as in result row processors. - TypeDecorator is present in the "sqlalchemy" import space.
* - whitespace removal bonanzaMike Bayer2011-01-021-13/+13
|
* - move sqlalchemy.test to test.libMike Bayer2010-11-151-4/+4
|
* - new oursql dialect added. [ticket:1613]Mike Bayer2009-11-101-2/+2
|
* - The "start" and "increment" attributes on Sequence nowMike Bayer2009-11-031-4/+64
| | | | | | generate "START WITH" and "INCREMENT BY" by default, on Oracle and Postgresql. Firebird doesn't support these keywords right now. [ticket:1545]
* - an executemany() now requires that all bound parameterMike Bayer2009-10-151-3/+12
| | | | | | | | | | | | sets require that all keys are present which are present in the first bound parameter set. The structure and behavior of an insert/update statement is very much determined by the first parameter set, including which defaults are going to fire off, and a minimum of guesswork is performed with all the rest so that performance is not impacted. For this reason defaults would otherwise silently "fail" for missing parameters, so this is now guarded against. [ticket:1566]
* - unit test fixesMike Bayer2009-10-101-1/+1
| | | | | - py3k readme - removed column.sequence accessor
* merge from branches/clauseelement-nonzeroPhilip Jenvey2009-09-241-2/+3
| | | | | | adds a __nonzero__ to _BinaryExpression to avoid faulty comparisons during hash collisions (which only occur on Jython) fixes #1547
* merge 0.6 series to trunk.Mike Bayer2009-08-061-65/+46
|
* - unit tests have been migrated from unittest to nose.Mike Bayer2009-06-101-0/+641
See README.unittests for information on how to run the tests. [ticket:970]
View Lorry Controller Status