summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* PEP8 tidy of test/sql/test_types.pypr/99Tony Locke2014-06-231-221/+256
|
* pg8000 passing test/sql/test_types.pyTony Locke2014-06-231-13/+11
| | | | | | | Opened up two tests that now pass with pg8000. Also, rewrote two tests to use actual tables rather than having a round trip in a single select statement. This is necessary for pg8000 because it sends strings to the server with type 'unknown' and lets the server work out the type.
* 0.9.5 released dateMike Bayer2014-06-231-0/+1
|
* fix changelogMike Bayer2014-06-231-0/+2
|
* - use new Or() directive to test for both SQL variants here, which can varyMike Bayer2014-06-211-7/+16
| | | | based on hash ordering of the ClassManager
* - fix test failuresMike Bayer2014-06-212-5/+5
|
* - Additional checks have been added for the case where an inheritingMike Bayer2014-06-2012-76/+218
| | | | | | | | | | mapper is implicitly combining one of its column-based attributes with that of the parent, where those columns normally don't necessarily share the same value. This is an extension of an existing check that was added via :ticket:`1892`; however this new check emits only a warning, instead of an exception, to allow for applications that may be relying upon the existing behavior. fixes #3042
* additional version notesMike Bayer2014-06-201-5/+5
|
* add missing version markersMike Bayer2014-06-201-0/+4
|
* - The :paramref:`.Column.nullable` flag is implicitly set to ``False``Mike Bayer2014-06-203-0/+31
| | | | | | | | | when that :class:`.Column` is referred to in an explicit :class:`.PrimaryKeyConstraint` for that table. This behavior now matches that of when the :class:`.Column` itself has the :paramref:`.Column.primary_key` flag set to ``True``, which is intended to be an exactly equivalent case. fixes #3023
* - Added a new type :class:`.postgresql.OID` to the Postgresql dialect.Mike Bayer2014-06-205-3/+41
| | | | | | | | While "oid" is generally a private type within PG that is not exposed in modern versions, there are some PG use cases such as large object support where these types might be exposed, as well as within some user-reported schema reflection use cases. fixes #3002
* - Fixed bug where column names added to ``mysql_length`` parameterMike Bayer2014-06-183-3/+51
| | | | | | | | on an index needed to have the same quoting for quoted names in order to be recognized. The fix makes the quotes optional but also provides the old behavior for backwards compatibility with those using the workaround. fixes #3085
* - Modified the behavior of :func:`.orm.load_only` such that primary keyMike Bayer2014-06-124-8/+66
| | | | | | | | | columns are always added to the list of columns to be "undeferred"; otherwise, the ORM can't load the row's identity. Apparently, one can defer the mapped primary keys and the ORM will fail, that hasn't been changed. But as load_only is essentially saying "defer all but X", it's more critical that PK cols not be part of this deferral. fixes #3080
* - changelogMike Bayer2014-06-081-0/+7
|
* Merged in univerio/sqlalchemy/materialized_paths (pull request #21) Mike Bayer2014-06-083-0/+136
|\ | | | | Materialized paths example
| * Materialized paths example.Jack Zhou2014-06-073-0/+136
| |
* | Update compiler.pyBY-jk2014-06-081-1/+2
| | | | | | | | | | | | Moved initialization into else block Conflicts: lib/sqlalchemy/sql/compiler.py
* | changelogMike Bayer2014-06-081-0/+8
| |
* | Merge branch 'master' of https://github.com/BY-jk/sqlalchemyMike Bayer2014-06-081-1/+1
|\ \ | |/ |/|
| * Wrong type usagepr/95BY-jk2014-05-301-1/+1
| | | | | | Wrong Type (TEXT) being used in StringTest
* | once kwarg in event funcs is new in 0.9.4Justin Wood (Callek)2014-06-051-2/+2
| | | | | | | | event.listen and event.listen_for have a kwarg once added in 0.9.4 (not 0.9.3) CHANGELOG agrees with this as well. (as does my manual testing)
* | - fix this test for MySQL, needs InnoDBMike Bayer2014-05-301-3/+7
| |
* | - remove drizzle dialectMike Bayer2014-05-3011-812/+155
| | | | | | | | | | - restore mysqldb fully within dialects/mysql/, it's no longer a connector. fixes #2984
* | - vastly improve the "safe close cursor" tests in test_reconnectMike Bayer2014-05-304-17/+74
| | | | | | | | | | | | | | | | | | | | | | - Fixed bug which would occur if a DBAPI exception occurs when the engine first connects and does its initial checks, and the exception is not a disconnect exception, yet the cursor raises an error when we try to close it. In this case the real exception would be quashed as we tried to log the cursor close exception via the connection pool and failed, as we were trying to access the pool's logger in a way that is inappropriate in this very specific scenario. fixes #3063
* | - The ``__mapper_args__`` dictionary is copied from a declarativeMike Bayer2014-05-303-1/+44
| | | | | | | | | | | | | | | | | | mixin or abstract class when accessed, so that modifications made to this dictionary by declarative itself won't conflict with that of other mappings. The dictionary is modified regarding the ``version_id_col`` and ``polymorphic_on`` arguments, replacing the column within with the one that is officially mapped to the local class/table. fixes #3062
* | fix typoMike Bayer2014-05-301-3/+3
| |
* | Merged in chrisw/sqlalchemy/more_range_docs (pull request #20) Mike Bayer2014-05-302-1/+31
|\ \ | | | | | | | | | | | | more docs for using psycopg2 range types, specifically instantiating models with them fixes #3046
| * | more docs for using psycopg2 range types, specifically instantiating models ↵Chris Withers2014-05-252-1/+31
| | | | | | | | | | | | with them
* | | - changelog + docs for pg8000 transaction isolation levelMike Bayer2014-05-304-2/+47
| | |
* | | Merge branch 'master' of https://github.com/tlocke/sqlalchemy into tlocke-masterMike Bayer2014-05-304-89/+98
|\ \ \
| * | | PEP 8 tidy of pg8000 dialect and postgresql/test_dialect.pypr/88Tony Locke2014-05-222-64/+51
| | | |
| * | | Autocommit isolation level for postgresql+pg8000Tony Locke2014-05-222-7/+37
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As with postgresql+psycopg2, execution_options(isolation_level='AUTOCOMMIT') now works for the postgresql+pg8000 dialect. Also enabled the autocommit test in test_dialect.py for pg8000.
| * | | Updated doc string for postgresql+pg8000 dialectTony Locke2014-05-211-10/+8
| | | |
| * | | 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 now passes test_extract() testTony Locke2014-05-211-1/+0
| | | |
| * | | Two tests now work for pg800 in EnumTestTony Locke2014-05-211-6/+0
| | | | | | | | | | | | | | | | | | | | The two tests, test_create_table() and test_unicode_labels() previously failed under pg8000, but now they pass, so this commit opens them up.
| * | | 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.
| * | | pg8000.dbapi is now just pg8000Tony Locke2014-05-211-1/+1
| | | |
* | | | update commentsMike Bayer2014-05-301-4/+6
| | | |
* | | | - The psycopg2 ``.closed`` accessor is now consulted when determiningMike Bayer2014-05-301-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | if an exception is a "disconnect" error; ideally, this should remove the need for any other inspection of the exception message to detect disconnect, however we will leave those existing messages in place as a fallback. This should be able to handle newer cases like "SSL EOF" conditions. Pull request courtesy Dirk Mueller. fixes #3021
* | | | Merge branch 'psycopg_disconnect' of https://github.com/dirkmueller/sqlalchemyMike Bayer2014-05-301-1/+5
|\ \ \ \
| * | | | Another Variant for detecting if a connection is closedpr/87Dirk Mueller2014-05-111-1/+5
| | |_|/ | |/| | | | | | | | | | | | | | | | | | | | | | If there is a closed attribute on the connection and it is true, return true. Implements a todo in the code and helps in one specific disconnect case where it previously did not match because the error message was "unknown error".
* | | | Merge branch 'master' into rel_1_0Mike Bayer2014-05-301-1/+1
|\ \ \ \
| * | | | revert this, not sure why that changedMike Bayer2014-05-301-1/+1
| | | | |
* | | | | Merge branch 'master' into rel_1_0Mike Bayer2014-05-308-38/+57
|\ \ \ \ \ | |/ / / /
| * | | | - Related to :ticket:`3060`, an adjustment has been made to the unitMike Bayer2014-05-308-38/+57
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | of work such that loading for related many-to-one objects is slightly more aggressive, in the case of a graph of self-referential objects that are to be deleted; the load of related objects is to help determine the correct order for deletion if passive_deletes is not set. - revert the changes to test_delete_unloaded_m2o, these deletes do in fact need to occur in the order of the two child objects first.
* | | | | Merge branch 'master' into rel_1_0Mike Bayer2014-05-302-10/+38
|\ \ \ \ \ | |/ / / /
| * | | | - add a new assertsql construct "Or", so that we can test for a UOW flushMike Bayer2014-05-302-10/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | that might take one of multiple directions; apply this to test_delete_unloaded_m2o which is now illustrating multiple paths due to #3060/#3061, though still doing the right thing.
* | | | | Merge branch 'master' into rel_1_0Mike Bayer2014-05-291-0/+2
|\ \ \ \ \ | |/ / / /
| * | | | add ticketMike Bayer2014-05-291-0/+2
| | | | |