summaryrefslogtreecommitdiff
path: root/lib/sqlalchemy/testing
Commit message (Collapse)AuthorAgeFilesLines
...
* mymysql dialectHajime Nakagami2013-03-011-1/+1
|
* - fix exclusion hereMike Bayer2013-02-062-8/+5
| | | | - mysql doesn't reset table counter here so test differently
* port numeric tests to dialect suiteMike Bayer2013-02-062-1/+181
|
* - adding in requirementsMike Bayer2013-02-064-3/+110
| | | | - get test_naturalpks to be more generalized
* - add support for pulling in an external requirements fileMike Bayer2013-02-062-6/+68
| | | | - start filling in default versions of remaining requirements that are still only in test/
* - cleanup HasSequence and move it to test_sequencesMike Bayer2013-02-062-42/+58
|
* - add an explicit test for sequences "optional"Mike Bayer2013-02-062-1/+27
|
* - add an "empty_inserts" requirement target plus a suite testMike Bayer2013-02-065-0/+153
| | | | - add suite tests for basic explicit Sequence support, result-row column access (tests that name_normalize is set correctly among many other things)
* - use SQL constructs here for databases that need to escape names like "data"Mike Bayer2013-01-271-5/+4
|
* - preparing for #695, modernize constraint/index testsMike Bayer2013-01-161-4/+9
|
* Fixed table reflection for Oracle when accessing a synonym that refersMike Bayer2012-12-091-2/+8
| | | | | | | | | | to a DBLINK remote database; while the syntax has been present in the Oracle dialect for some time, up until now it has never been tested. The syntax has been tested against a sample database linking to itself, however there's still some uncertainty as to what should be used for the "owner" when querying the remote database for table information. Currently, the value of "username" from user_db_links is used to match the "owner". [ticket:2619]
* internally at least refer to multirow as "multivalues", to distinguish betweenMike Bayer2012-12-081-2/+2
| | | | | an INSERT that's used in executemany() as opposed to one which has a VALUES clause with multiple entries.
* - multivalued inserts, [ticket:2623]Mike Bayer2012-12-081-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - update "not supported" messages for empty inserts, mutlivalue inserts - rework the ValuesBase approach for multiple value sets so that stmt.parameters does store a list for multiple values; the _has_multiple_parameters flag now indicates which of the two modes the statement is within. it now raises exceptions if a subsequent call to values() attempts to call a ValuesBase with one mode in the style of the other mode; that is, you can't switch a single- or multi- valued ValuesBase to the other mode, and also if a multiple value is passed simultaneously with a kwargs set. Added tests for these error conditions - Calling values() multiple times in multivalue mode now extends the parameter list to include the new parameter sets. - add error/test if multiple *args were passed to ValuesBase.values() - rework the compiler approach for multivalue inserts, back to where _get_colparams() returns the same list of (column, value) as before, thereby maintaining the identical number of append() and other calls when multivalue is not enabled. In the case of multivalue, it makes a last-minute switch to return a list of lists instead of the single list. As it constructs the additional lists, the inline defaults and other calculated default parameters of the first parameter set are copied into the newly generated lists so that these features continue to function for a multivalue insert. Multivalue inserts now add no additional function calls to the compilation for regular insert constructs. - parameter lists for multivalue inserts now includes an integer index for all parameter sets. - add detailed documentation for ValuesBase.values(), including careful wording to describe the difference between multiple values and an executemany() call. - add a test for multivalue insert + returning - it works ! - remove the very old/never used "postgresql_returning"/"firebird_returning" flags.
* juts a 'expected 2 blank lines' pep8 passDiana Clarke2012-11-191-1/+16
|
* just a pep8 pass of lib/sqlalchemy/testing/Diana Clarke2012-11-198-17/+96
|
* just a pep8 pass of lib/sqlalchemy/testing/Diana Clarke2012-11-1912-47/+93
|
* - hstore adjustmentsMike Bayer2012-11-171-4/+4
|
* fix some oracle-related tests, but still need to fix unhashable_types testMike Bayer2012-11-121-2/+2
|
* - support "fails_if" requirements as __requires__; so far this just skips, ↵Mike Bayer2012-11-123-3/+166
| | | | | | | | | | doesn't actually run the test - add requirements for date/datetime/time capabilities - remove test/sql/test_types->DateTest and create new tests in suite/test_types - move the StringTest with the "no length create" test to the suite, though this is a weird test
* - rework the sphinx customizations into distinct modulesMike Bayer2012-10-192-4/+18
| | | | | | | - build a new Sphinx extension that allows dialect info to be entered as directives which is then rendered consistently throughout all dialect/dbapi sections - break out the "empty_strings" requirement for oracle test
* - break out unicode tests to a varchar + a text test, add a requiresMike Bayer2012-10-152-18/+28
|
* fix for pypy/jython gc_collectMike Bayer2012-10-151-2/+2
|
* - add some UPDATE..FROM tests and also some new reqsMike Bayer2012-10-121-0/+21
|
* - create new sqlalchemy.testing.suite.test_types, starting with Unicode ↵Mike Bayer2012-10-103-0/+110
| | | | | | | round trip tests. - clean out existing test_types:UnicodeTest to be strictly individual unit tests against Unicode(), String(), etc. with no database access.
* - [feature] Added "collation" parameter to allMike Bayer2012-10-101-0/+6
| | | | | | | | | | | String types. When present, renders as COLLATE <collation>. This to support the COLLATE keyword now supported by several databases including MySQL, SQLite, and Postgresql. [ticket:2276] - [change] The Text() type renders the length given to it, if a length was specified.
* - [feature] Added TIME type to mysql dialect,Mike Bayer2012-10-101-1/+1
| | | | | | | | | | | | accepts "fst" argument which is the new "fractional seconds" specifier for recent MySQL versions. The datatype will interpret a microseconds portion received from the driver, however note that at this time most/all MySQL DBAPIs do not support returning this value. [ticket:2534] - attempted to modernize the types tests in test_mysql a little, though has a long way to go
* missing with_statementMike Bayer2012-10-081-0/+2
|
* - add a nifty contextmanager form of assert_execution/assert_statement_countMike Bayer2012-10-081-0/+11
|
* - [feature] Various API tweaks to the "dialect"Mike Bayer2012-10-081-6/+16
| | | | | | | API to better support highly specialized systems such as the Akiban database, including more hooks to allow an execution context to access type processors.
* - add back __engine_options__Mike Bayer2012-10-044-15/+79
| | | | | - break test_insert tests into explicitly get_lastrowid() vs. implicit_returning tests, fix up requirements to split them out
* - connect immediately on _create_testing_engine to initialize dialect ↵Mike Bayer2012-10-042-1/+1
| | | | capabilities
* - don't call get_lastrowid() on explicit returningMike Bayer2012-10-043-2/+10
| | | | | | - don't hardwire "subqueries" requirement in the base, mysql < 4.1 isn't working anyway - don't need explicit FB/PG exclusions in test_returning - hit db.connect() for the returning requirement
* - test updatesMike Bayer2012-10-044-49/+102
|
* - requirementsMike Bayer2012-10-033-3/+24
|
* - fix the fixture here that wasn't creating consistentlyMike Bayer2012-10-012-14/+22
| | | | | | | - rewrite --dropfirst to be more industrial strength, includes views - fix order_by="foreign_key" to maintain the same ordering as metadata.sorted_tables. Not ideal that this was the other way throughout 0.7 but this is still a little-used method, in contrast to metadata.sorted_tables.
* allow variability hereMike Bayer2012-09-301-0/+7
|
* mssql: - [bug] Fixed bug where reflection of primary key constraintMike Bayer2012-09-302-2/+2
| | | | | | | would double up columns if the same constraint/table existed in multiple schemas. - force returns_rows to False for inserts where we know rows shouldnt be returned; allows post_exec() to use the cursor without issue
* put this inside a main()Mike Bayer2012-09-301-1/+2
|
* consolidate config into noseplugin, remove the dupe, load noseplugin using ↵Mike Bayer2012-09-302-205/+192
| | | | imp.load_source(), see if that works
* 2.5 supportMike Bayer2012-09-303-4/+9
|
* also get rid of satest.cfgMike Bayer2012-09-291-1/+1
|
* mergeMike Bayer2012-09-291-2/+0
|
* - rework component reflection test so that usual framework hooks can be usedMike Bayer2012-09-291-59/+49
| | | | to redefine tables, etc.
* devMike Bayer2012-09-292-154/+182
|
* adjustmentsMike Bayer2012-09-293-3/+14
|
* getting everything to pass againMike Bayer2012-09-271-2/+1
|
* - more tests, move some tests out of test_reflection, test_queryMike Bayer2012-09-2716-169/+773
|
* display name in messageMike Bayer2012-09-271-1/+2
|
* - add a runner moduleMike Bayer2012-09-273-2/+33
| | | | - make "default" the default dialect.
* tweaksMike Bayer2012-09-272-5/+11
|
View Lorry Controller Status