summaryrefslogtreecommitdiff
path: root/lib/sqlalchemy/dialects
Commit message (Collapse)AuthorAgeFilesLines
* ReST fix: missing backtickpr/251Marius Gedminas2016-03-211-1/+1
| | | Fixes a misrendering at http://docs.sqlalchemy.org/en/latest/dialects/mssql.html#nullability:
* - Added basic isolation level support to the SQL Server dialectsMike Bayer2016-03-151-0/+86
| | | | | | via :paramref:`.create_engine.isolation_level` and :paramref:`.Connection.execution_options.isolation_level` parameters. fixes #3534
* - changelog and docs for #3332, fixes #3332Mike Bayer2016-03-152-13/+39
| | | | | | - make docs for isolation level more consistent between postgresql and mysql - move mysql autocommit tests
* Merge branch 'master' into pr157Mike Bayer2016-03-1554-2645/+3635
|\
| * - add notes for pyodbc limitations with rowcount fixes #3675Mike Bayer2016-03-152-0/+41
| |
| * - py3k fix for enum featureMike Bayer2016-02-081-1/+4
| |
| * - add an impl for Enum to Oracle which has subclassing requirementsMike Bayer2016-02-041-0/+13
| | | | | | | | | | | | | | on unicode. Enum would be better as a TypeDecorator at this point but then that becomes awkward with native enum types (Interval works that way, but we don't need the bind_processor for native interval...)
| * Merge branch 'master' of https://bitbucket.org/carlrivers/sqlalchemyMike Bayer2016-02-021-2/+1
| |\
| | * Merged zzzeek/sqlalchemy into masterCarlos Rivas2016-01-2618-1697/+1795
| | |\
| | * | Removed entry that causes AttributeError (#3621) - Oracle zxJDBC fails with ↵Carlos Rivas2016-01-231-2/+1
| | | | | | | | | | | | | | | | AttributeError in object OracleCompiler_zxjdbc
| * | | - add changelog and migration notes for new Enum features,Mike Bayer2016-02-021-25/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | fixes #3095, #3292 - reorganize enum constructor to again work with the MySQL ENUM type - add a new create_constraint flag to Enum to complement that of Boolean - reinstate the CHECK constraint tests for enum, these already fail /skip against the MySQL backend - simplify lookup rules in Enum, have them apply to all varieties of Enum equally
| * | | - The ``sqlalchemy.dialects.postgres`` module, long deprecated, isMike Bayer2016-01-292-18/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | removed; this has emitted a warning for many years and projects should be calling upon ``sqlalchemy.dialects.postgresql``. Engine URLs of the form ``postgres://`` will still continue to function, however.
| * | | - happy new yearMike Bayer2016-01-2953-53/+53
| | |/ | |/|
| * | - The workaround for right-nested joins on SQLite, where they are rewrittenMike Bayer2016-01-261-6/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | as subqueries in order to work around SQLite's lack of support for this syntax, is lifted when SQLite version 3.7.16 or greater is detected. fixes #3634 - The workaround for SQLite's unexpected delivery of column names as ``tablename.columnname`` for some kinds of queries is now disabled when SQLite version 3.10.0 or greater is detected. fixes #3633
| * | - documenation updates to clarify specific SQLite versionsMike Bayer2016-01-211-2/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | that have problems with right-nested joins and UNION column keys; references #3633 references #3634. backport from 1.1 to 0.9 announcing 1.1 as where these behaviors will be retired based on version-specific checks - fix test_resultset so that it passes when SQLite 3.10.0 is present, references #3633
| * | - The unsupported Sybase dialect now raises ``NotImplementedError``Mike Bayer2016-01-201-5/+1
| | | | | | | | | | | | | | | when attempting to compile a query that includes "offset"; Sybase has no straightforward "offset" feature. fixes #2278
| * | - update oracle JDBC driver URL, fixes #3554Mike Bayer2016-01-201-2/+1
| | |
| * | Fix ArrayOfEnum's handling of empty arrays.pr/229Chase2016-01-191-1/+1
| | | | | | | | | Prior to this change a value of `'{}'` would split into the list `['']`.
| * | Remove quote on first DATEPART paramaterGuillaume DOUMENC2016-01-121-1/+1
| | |
| * | - reorganize schema_translate_map to be succinct and gain the performanceMike Bayer2016-01-111-2/+2
| | | | | | | | | | | | back by using an attrgetter for the default case
| * | - Multi-tenancy schema translation for :class:`.Table` objects is added.Mike Bayer2016-01-081-5/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | This supports the use case of an application that uses the same set of :class:`.Table` objects in many schemas, such as schema-per-user. A new execution option :paramref:`.Connection.execution_options.schema_translate_map` is added. fixes #2685 - latest tox doesn't like the {posargs} in the profile rerunner
| * | - pg8000 fixes for jsonMike Bayer2016-01-071-0/+1
| | |
| * | - Added a new entrypoint system to the engine to allow "plugins" toMike Bayer2016-01-061-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | be stated in the query string for a URL. Custom plugins can be written which will be given the chance up front to alter and/or consume the engine's URL and keyword arguments, and then at engine create time will be given the engine itself to allow additional modifications or event registration. Plugins are written as a subclass of :class:`.CreateEnginePlugin`; see that class for details. fixes #3536
| * | - Added :class:`.mysql.JSON` for MySQL 5.7. The JSON type providesMike Bayer2016-01-069-191/+218
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | persistence of JSON values in MySQL as well as basic operator support of "getitem" and "getpath", making use of the ``JSON_EXTRACT`` function in order to refer to individual paths in a JSON structure. fixes #3547 - Added a new type to core :class:`.types.JSON`. This is the base of the PostgreSQL :class:`.postgresql.JSON` type as well as that of the new :class:`.mysql.JSON` type, so that a PG/MySQL-agnostic JSON column may be used. The type features basic index and path searching support. fixes #3619 - reorganization of migration docs etc. to try to refer both to the fixes to JSON that helps Postgresql while at the same time indicating these are new features of the new base JSON type. - a rework of the Array/Indexable system some more, moving things that are specific to Array out of Indexable. - new operators for JSON indexing added to core so that these can be compiled by the PG and MySQL dialects individually - rename sqltypes.Array to sqltypes.ARRAY - as there is no generic Array implementation, this is an uppercase type for now, consistent with the new sqltypes.JSON type that is also not a generic implementation. There may need to be some convention change to handle the case of datatypes that aren't generic, rely upon DB-native implementations, but aren't necessarily all named the same thing.
| * | - break out mysql/base into modules as it's getting huge with more to comeMike Bayer2016-01-044-1488/+1534
| |/
| * - An adjustment to the regular expression used to parse MySQL views,Mike Bayer2015-12-221-1/+1
| | | | | | | | | | | | | | such that we no longer assume the "ALGORITHM" keyword is present in the reflected view source, as some users have reported this not being present in some Amazon RDS environments. fixes #3613
| * Add new reserved words for MySQL 5.7.pr/222Hanno Schlichting2015-12-141-0/+2
| |
| * - Fixed bug in MySQL reflection where the "fractional sections portion"Mike Bayer2015-12-071-0/+5
| | | | | | | | | | | | | | | | of the :class:`.mysql.DATETIME`, :class:`.mysql.TIMESTAMP` and :class:`.mysql.TIME` types would be incorrectly placed into the ``timestamp`` attribute, which is unused by MySQL, instead of the ``fsp`` attribute. fixes #3602
| * - Added the error "20006: Write to the server failed" to the listMike Bayer2015-11-301-1/+2
| | | | | | | | | | | | of disconnect errors for the pymssql driver, as this has been observed to render a connection unusable. fixes #3585
| * Merge remote-tracking branch 'origin/pr/216'Mike Bayer2015-11-301-1/+1
| |\
| | * - Postgres: Do not prefix table with schema in: "FOR UPDATE of <table>"pr/216Diana Clarke2015-11-241-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For example, this query: SELECT s1.users.name FROM s1.users FOR UPDATE OF s1.users should actually be: SELECT s1.users.name FROM s1.users FOR UPDATE OF users fixes #3573
| * | Merge remote-tracking branch 'origin/pr/215'Mike Bayer2015-11-301-1/+1
| |\ \
| | * | fix postgresql exclude contraint to check when= against None rather than ↵pr/215aisch2015-11-231-1/+1
| | |/ | | | | | | | | | __bool__ eval
| * | - A descriptive ValueError is now raised in the event that SQL serverMike Bayer2015-11-301-2/+10
| |/ | | | | | | | | | | | | returns an invalid date or time format from a DATE or TIME column, rather than failing with a NoneType error. Pull request courtesy Ed Avis. pullreq github:206
| * - Fixed the ``.python_type`` attribute of :class:`.postgresql.INTERVAL`Mike Bayer2015-11-191-0/+6
| | | | | | | | | | | | | | | | | | to return ``datetime.timedelta`` in the same way as that of :obj:`.types.Interval.python_type`, rather than raising ``NotImplementedError``. fixes #3571 (cherry picked from commit 29d6f6e19b014bb5ce79032bd8803e32b4da0e5e)
| * - Added support for reflecting the source of materialized viewsMike Bayer2015-11-181-5/+21
| | | | | | | | | | | | to the Postgresql version of the :meth:`.Inspector.get_view_definition` method. fixes #3587
| * - extend pullreq github:213 to also include DATETIMEOFFSET and TIME,Mike Bayer2015-11-141-2/+2
| | | | | | | | | | | | which also accept zero precision - extend test case here to include a backend-agnostic suite - changelog for MSSQL date fix
| * Pass precision value to mssql.DATETIME2 when it is 0pr/213Jacobo de Vera2015-11-131-1/+1
| | | | | | | | | | The simple check on the precision results in DATETIME2(0) generating a DATETIME2 column, with default precision, which is 7.
| * Updated PostgreSQL links to point to "current" rather than hardcoded versionJeff Widman2015-11-051-2/+2
| |
| * Update links in SQLAlchemy docs that point to postgres docs to use 'devel' ↵Jeff Widman2015-11-041-2/+2
| | | | | | | | rather than hardcoded version
| * - cross-linking for pool recycle featureMike Bayer2015-10-301-0/+5
| |
| * Merge remote-tracking branch 'origin/pr/208'Mike Bayer2015-10-081-1/+1
| |\
| | * Update base.pypr/208Peter Demin2015-10-071-1/+1
| | | | | | | | | Docstring typo keysowrds => keywords
| * | - for DB's w/o a real "autoincrement", reflection should be returningMike Bayer2015-10-073-3/+3
| |/ | | | | | | "auto", doesn't matter if there's a default here
| * - The system by which a :class:`.Column` considers itself to be anMike Bayer2015-10-072-38/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | "auto increment" column has been changed, such that autoincrement is no longer implicitly enabled for a :class:`.Table` that has a composite primary key. In order to accommodate being able to enable autoincrement for a composite PK member column while at the same time maintaining SQLAlchemy's long standing behavior of enabling implicit autoincrement for a single integer primary key, a third state has been added to the :paramref:`.Column.autoincrement` parameter ``"auto"``, which is now the default. fixes #3216 - The MySQL dialect no longer generates an extra "KEY" directive when generating CREATE TABLE DDL for a table using InnoDB with a composite primary key with AUTO_INCREMENT on a column that isn't the first column; to overcome InnoDB's limitation here, the PRIMARY KEY constraint is now generated with the AUTO_INCREMENT column placed first in the list of columns.
| * - Fixed bug in Oracle dialect where reflection of tables and otherMike Bayer2015-10-051-0/+3
| | | | | | | | | | | | | | | | symbols with names quoted to force all-lower-case would not be identified properly in reflection queries. The :class:`.quoted_name` construct is now applied to incoming symbol names that detect as forced into all-lower-case within the "name normalize" process. fixes #3548
| * - limit the search for schemas to not include "temp", which is sort of an ↵Mike Bayer2015-09-281-6/+20
| | | | | | | | | | | | | | | | | | | | implicit schema - repair the CREATE INDEX ddl for schemas - update provisioning to include support for setting up ATTACH DATABASE up front for the test_schema; enable "schemas" testing for SQLite - changelog / migration notes for new SQLite schema support - include the "schema" as the "remote_schema" when we reflect SQLite FKs
| * Merge remote-tracking branch 'origin/pr/198' into pr198Mike Bayer2015-09-281-0/+7
| |\
| | * Support get_schema_names for SQLiteBrian Van Klaveren2015-09-091-0/+7
| | |
| * | - The ``legacy_schema_aliasing`` flag, introduced in version 1.0.5Mike Bayer2015-09-191-67/+37
| | | | | | | | | | | | | | | | | | | | | as part of :ticket:`3424` to allow disabling of the MSSQL dialect's attempts to create aliases for schema-qualified tables, now defaults to False; the old behavior is now disabled unless explicitly turned on. fixes #3434
View Lorry Controller Status