summaryrefslogtreecommitdiff
path: root/test/requirements.py
Commit message (Collapse)AuthorAgeFilesLines
* - add a skip for JSONB on pg8000 if we are on 1.10.1 or earlierMike Bayer2015-03-021-0/+8
|
* - Added support for the :class:`postgresql.JSONB` datatype whenMike Bayer2015-01-311-0/+6
| | | | | | | | | | | | | | | | | using psycopg2 2.5.4 or greater, which features native conversion of JSONB data so that SQLAlchemy's converters must be disabled; additionally, the newly added psycopg2 extension ``extras.register_default_jsonb`` is used to establish a JSON deserializer passed to the dialect via the ``json_deserializer`` argument. Also repaired the Postgresql integration tests which weren't actually round-tripping the JSONB type as opposed to the JSON type. Pull request courtesy Mateusz Susik. - Repaired the use of the "array_oid" flag when registering the HSTORE type with older psycopg2 versions < 2.4.3, which does not support this flag, as well as use of the native json serializer hook "register_default_json" with user-defined ``json_deserializer`` on psycopg2 versions < 2.5, which does not include native json.
* - additional test adjustments for pypy / psycopg2cffi. ThisMike Bayer2015-01-261-0/+4
| | | | | | | | | | consists mainly of adjusting fixtures to ensure connections are closed explicitly. psycopg2cffi also handles unicode bind parameter names differently than psycopg2, and seems to possibly have a little less control over floating point values at least in one test which is marked as a "fail", though will see if it runs differently on linux than osx.. - changelog for psycopg2cffi, fixes #3052
* Added psycopg2cffi dialectShaun Stanworth2015-01-261-0/+4
|
* - SQL Server 2012 now recommends VARCHAR(max), NVARCHAR(max),Mike Bayer2014-12-061-0/+12
| | | | | | | VARBINARY(max) for large text/binary types. The MSSQL dialect will now respect this based on version detection, as well as the new ``deprecate_large_types`` flag. fixes #3039
* - enhance only_on() to work with compound specsMike Bayer2014-12-061-3/+9
| | | | - fix "temporary_tables" requirement
* Merge remote-tracking branch 'origin/pr/151' into pr151Mike Bayer2014-12-011-0/+11
|\
| * Merge branch 'master' into fdbsql-testsScott Dugas2014-11-031-2/+27
| |\ | | | | | | | | | | | | Conflicts: lib/sqlalchemy/testing/exclusions.py
| * | Added requirement for temporary tablesScott Dugas2014-10-301-0/+5
| | |
| * | Added new requirement for check_constraintsScott Dugas2014-10-231-0/+6
| | |
* | | - fix minor spelling errorJon Nelson2014-11-141-1/+1
| |/ |/|
* | - added new backend for pysqlcipher, as we will probably getMike Bayer2014-10-291-2/+2
| | | | | | | | requests for it soon.
* | - Mysqlconnector as of version 2.0, probably as a side effect ofMike Bayer2014-10-121-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | the python 3 merge, now does not expect percent signs (e.g. as used as the modulus operator and others) to be doubled, even when using the "pyformat" bound parameter format (this change is not documented by Mysqlconnector). The dialect now checks for py2k and for mysqlconnector less than version 2.0 when detecting if the modulus operator should be rendered as ``%%`` or ``%``. - Unicode SQL is now passed for MySQLconnector version 2.0 and above; for Py2k and MySQL < 2.0, strings are encoded. Note that mysqlconnector as of 2.0.1 appears to have a bug with unicode DDL on py2k, so the tests here are skipping until we observe it's fixed. - take out profiling on mysqlconnector, callcounts vary too much with its current development speed
* | - Added support for the Oracle table option ON COMMIT. This is beingMike Bayer2014-09-171-1/+1
| | | | | | | | | | | | | | | | | | kept separate from Postgresql's ON COMMIT for now even though ON COMMIT is in the SQL standard; the option is still very specific to temp tables and we eventually would provide a more first class temporary table feature. - oracle can apparently do get_temp_table_names() too, so implement that, fix its get_table_names(), and add it to #3204. fixes #3204 again.
* | - Added :meth:`.Inspector.get_temp_table_names` andMike Bayer2014-09-171-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | :meth:`.Inspector.get_temp_view_names`; currently, only the SQLite dialect supports these methods. The return of temporary table and view names has been **removed** from SQLite's version of :meth:`.Inspector.get_table_names` and :meth:`.Inspector.get_view_names`; other database backends cannot support this information (such as MySQL), and the scope of operation is different in that the tables can be local to a session and typically aren't supported in remote schemas. fixes #3204
* | Fixing some pep8s and adding get_foreign_tables.Rodrigo Menezes2014-09-031-1/+1
| |
* | Merge branch 'master' of https://github.com/zzzeek/sqlalchemy into ↵Rodrigo Menezes2014-08-261-11/+0
|\ \ | |/ | | | | feature/postgres-relkind
| * two_phase_recover, COMMIT PREPARED in transactionTony Locke2014-08-021-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | In test/engine/test_transaction/test_two_phase_recover(), a COMMIT PREPARED is issued while in a transaction. This causes an error, and a prepared transaction is left hanging around which causes the subsequent test to hang. I've altered the test to execute the offending query with autocommit=true, then when it gets to the COMMIT PRPARED it can go ahead. There's another complication for pg8000 because its tpc_recover() method started a transaction if one wasn't already in progress. I've decided that this is incorrect behaviour and so from pg8000-1.9.13 this method never starts or stops a transaction.
| * With pg8000-1.9.13 passes engine/test_reconnectTony Locke2014-08-021-10/+0
| | | | | | | | | | | | | | The pg8000 dialect checks the text of the exception to determine if the connection is closed. I'd (recklessly!) changed the text of the exception in a recent version of the pg8000 driver adding capitalization and a full stop. I've changed it back now so all works.
* | Added support for postgres_relkind.Rodrigo Menezes2014-08-141-0/+8
|/
* - add support for tags, including include/exclude support.Mike Bayer2014-07-271-12/+2
| | | | simplify tox again now that we can exclude tests more easily
* - rework the exclusions system to have much better support for compoundMike Bayer2014-07-261-12/+15
| | | | rules, better message formatting
* - more pg8000 tests passingMike Bayer2014-07-251-0/+10
|
* - update some SQL server tests, supportMike Bayer2014-07-221-2/+8
| | | | - add support for IDENTITY INSERT setting for INSERT with inline VALUES
* - Fixed bug introduced in 0.9.5 by new pg8000 isolation level featureMike Bayer2014-07-211-0/+1
| | | | | where engine-level isolation level parameter would raise an error on connect. fixes #3134
* Add postgresql+pg8000 to floats_to_four_decimalsTony Locke2014-05-211-2/+5
| | | | | pg8000 uses binary transfer of floats and so accuracy is lost for floats that can't be represented exactly in binary.
* pg8000 no longer truncates decimalsTony Locke2014-05-211-2/+0
| | | | | We can now update the requirements to remove the special case of pg8000 truncating decimals.
* - Fixed ORM bug where changing the primary key of an object, then markingMike Bayer2014-03-281-1/+8
| | | | | | | | | | | | | it for DELETE would fail to target the correct row for DELETE. Then to compound matters, basic "number of rows matched" checks were not being performed. Both issues are fixed, however note that the "rows matched" check requires so-called "sane multi-row count" functionality; the DBAPI's executemany() method must count up the rows matched by individual statements and SQLAlchemy's dialect must mark this feature as supported, currently applies to some mysql dialects, psycopg2, sqlite only. fixes #3006 - Enabled "sane multi-row count" checking for the psycopg2 DBAPI, as this seems to be supported as of psycopg2 2.0.9.
* - Tweaked the settings for mysql-connector-python; in Py2K, theMike Bayer2014-03-271-8/+10
| | | | | | | | | | | "supports unicode statements" flag is now False, so that SQLAlchemy will encode the *SQL string* (note: *not* the parameters) to bytes before sending to the database. This seems to allow all unicode-related tests to pass for mysql-connector, including those that use non-ascii table/column names, as well as some tests for the TEXT type using unicode under cursor.executemany(). - other mysql-connector fixes; latest version seems to do better on function call counts
* fix some mysqlconnector failuresMike Bayer2014-03-241-4/+10
|
* - move some requirements up to the testing module to better support runningMike Bayer2014-03-131-32/+0
| | | | SQLA internal tests outside; plus things like savepoints, twophase
* - add more support for suite tests, moving some tests from test_query out to ↵Mike Bayer2014-03-131-0/+19
| | | | | | suite and adding some more requirements
* - Support has been added for pytest to run tests. This runnerMike Bayer2014-03-031-18/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | is currently being supported in addition to nose, and will likely be preferred to nose going forward. The nose plugin system used by SQLAlchemy has been split out so that it works under pytest as well. There are no plans to drop support for nose at the moment and we hope that the test suite itself can continue to remain as agnostic of testing platform as possible. See the file README.unittests.rst for updated information on running tests with pytest. The test plugin system has also been enhanced to support running tests against mutiple database URLs at once, by specifying the ``--db`` and/or ``--dburi`` flags multiple times. This does not run the entire test suite for each database, but instead allows test cases that are specific to certain backends make use of that backend as the test is run. When using pytest as the test runner, the system will also run specific test suites multiple times, once for each database, particularly those tests within the "dialect suite". The plan is that the enhanced system will also be used by Alembic, and allow Alembic to run migration operation tests against multiple backends in one run, including third-party backends not included within Alembic itself. Third party dialects and extensions are also encouraged to standardize on SQLAlchemy's test suite as a basis; see the file README.dialects.rst for background on building out from SQLAlchemy's test platform.
* add a skip for oracle on thisMike Bayer2014-02-011-0/+21
|
* - support addition of fails_if()/only_on(), just wraps the decoratorsMike Bayer2014-01-021-4/+10
| | | | - update a few exclusions to support current pymssql. passes all of test_suite and dialect/mssql
* - apply a similar fix for floats to mssql+pyodbc as we did to firebirdMike Bayer2013-12-281-1/+11
| | | | | - wrangle through osx+pyodbc+freetds to get at least test_suite to pass again with mssql+pyodbc. invovled adding some silly requirements
* - The "asdecimal" flag used with the :class:`.Float` type will nowMike Bayer2013-12-271-2/+12
| | | | | | work with Firebird dialects; previously the decimal conversion was not occurring. - scale back some firebird FP numeric tests
* - repair some suite tests for firebirdMike Bayer2013-12-271-3/+15
|
* - The precision used when coercing a returned floating point value toMike Bayer2013-11-221-0/+7
| | | | | | | | | | Python ``Decimal`` via string is now configurable. The flag ``decimal_return_scale`` is now supported by all :class:`.Numeric` and :class:`.Float` types, which will ensure this many digits are taken from the native floating point value when it is converted to string. If not present, the type will make use of the value of ``.scale``, if the type supports this setting and it is non-None. Otherwise the original default length of 10 is used. [ticket:2867]
* - remove informix dialect, moved out to ↵Mike Bayer2013-11-171-7/+2
| | | | | | https://bitbucket.org/zzzeek/sqlalchemy_informixdb - remove informix, maxdb, access symbols from tests etc.
* - The typing system now handles the task of rendering "literal bind" values,Mike Bayer2013-10-201-0/+9
| | | | | | | | | | | | | | | e.g. values that are normally bound parameters but due to context must be rendered as strings, typically within DDL constructs such as CHECK constraints and indexes (note that "literal bind" values become used by DDL as of :ticket:`2742`). A new method :meth:`.TypeEngine.literal_processor` serves as the base, and :meth:`.TypeDecorator.process_literal_param` is added to allow wrapping of a native literal rendering method. [ticket:2838] - enhance _get_colparams so that we can send flags like literal_binds into INSERT statements - add support in PG for inspecting standard_conforming_strings - add a new series of roundtrip tests based on INSERT of literal plus SELECT for basic literal rendering in dialect suite
* - Removed some now unneeded version checks [ticket:2829] courtesy alex gaynorMike Bayer2013-09-221-14/+0
|
* - assorted fixes raised by pypy 2.1beta2, but all of which are goodMike Bayer2013-08-011-2/+3
| | | | | | | | | | | | | | | ideas in general: - pypy2.1 w/ sqlite3 is the first DBAPI we're seeing returning unicode in cursor.description without being py3k. add a new on-connect check for this, if we get back a u"", just don't do description decoding, should be OK for now. - the set tests in test_collection were assuming the two sets would be ordered the same when it tested pop(), can't really assume that. - test_serializer gets worse and worse, pickle is just not really viable here, ding out pypy - pypy2.1b2 seems to allow cursor.lastrowid to work (or we changed something?) - pool._threadconns.current() is a weakref, it can be None - another one of those logging.handlers imports
* make this rule automatic based on coverage pluginMike Bayer2013-07-031-5/+8
|
* add a float exclusion to help oursql build 100%Mike Bayer2013-07-021-0/+3
|
* mark the tests that seem to be segfauling py3k+coverage so that we can ↵Mike Bayer2013-06-301-0/+9
| | | | | | exclude them at the nose command line
* this locale is not needed. maybe it is somewhere but the locale I have ↵Mike Bayer2013-06-221-5/+0
| | | | | | ("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-221-0/+15
|\ | | | | Support for Postgres range types.
| * Basic type support for the new range types in postgres 9.2Chris Withers2013-06-101-0/+15
| |
* | turn this requirement back down as the simpler serialize works better nowMike Bayer2013-06-171-7/+0
| |
View Lorry Controller Status