| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
- add pg8000 version detection for the "sane multi rowcount" feature
|
|\ |
|
| |
| |
| |
| |
| | |
From pg8000-1.9.14 sane_multi_rowcount is supported so this commit
updates the dialect accordingly.
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
Conflicts:
doc/build/changelog/changelog_10.rst
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- return a list of dicts like other methods do
- don't combine 'schema' with 'name', leave them separate
- support '*' argument so that we can retrieve cross-schema
if needed
- remove "conn" argument
- use bound parameters for 'schema' in SQL
- order by schema, name, label
- adapt _load_enums changes to column reflection
- changelog
- module docs for get_enums()
- add drop of enums to --dropfirst
|
| | |
| | |
| | |
| | |
| | | |
Provide opportunity to get enums list via an inspector instance public
interface.
|
| | | |
|
|/ / |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
otherwise render a SQL NULL column value, rather than a JSON-encoded
``'null'``. To support this case, changes are as follows:
* The value :func:`.null` can now be specified, which will always
result in a NULL value resulting in the statement.
* A new parameter :paramref:`.JSON.none_as_null` is added, which
when True indicates that the Python ``None`` value should be
peristed as SQL NULL, rather than JSON-encoded ``'null'``.
Retrival of NULL as None is also repaired for DBAPIs other than
psycopg2, namely pg8000.
fixes #3159
|
|/
|
|
| |
ref #3155
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
The postgresql base dialect has problems with two-phase commit because
there isn't a standard way of handling autocommit in DBAPI. This commit
modifies the pg8000 dialect to use the DBAPI tpc extension, which is
supported by pg8000 as of version 1.9.11.
|
|\ \ |
|
| | |
| | |
| | | |
array.__init__() expects a list as its sole parameter but inside _bind_param(), instead of sending a list it's sending each item in the list as a separate argument which is incorrect.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
events from firing for those statements which it uses internally
to detect if a table exists or not. This is achieved using an
execution option ``skip_user_error_events`` that disables the handle
error event for the scope of that execution. In this way, user code
that rewrites exceptions doesn't need to worry about the MySQL
dialect or other dialects that occasionally need to catch
SQLAlchemy specific exceptions.
|
| |
| |
| |
| | |
- add support for IDENTITY INSERT setting for INSERT with inline VALUES
|
| |
| |
| |
| |
| | |
where engine-level isolation level parameter would raise an error
on connect. fixes #3134
|
|/
|
|
| |
sqlalchemy/orm, sqlalchemy/event, sqlalchemy/testing
|
|
|
|
|
|
|
| |
query used to determine "default schema" is invalid in SQL Server 2000.
For SQL Server 2000 we go back to defaulting to the "schema name"
parameter of the dialect, which is configurable but defaults
to 'dbo'. fixes #3025
|
|
|
|
|
|
|
|
|
| |
statements which operate when an explicit INSERT is being
interjected into an IDENTITY column, to support non-ascii table
identifiers on drivers such as pyodbc + unix + py2k that don't
support unicode statements.
ref #3091 as this fix is also in that issue's patch, but is
a different issue.
|
|
|
|
|
|
|
|
|
| |
for the ``description_encoding`` dialect parameter, which when
not explicitly set was preventing cursor.description from
being parsed correctly in the case of result sets that
contained names in alternate encodings. This parameter
shouldn't be needed going forward.
fixes #3091
|
|
|
|
|
|
|
| |
subclasses where direct association of the type with a
:class:`.MetaData` would lead to a hang when events
(like create events) were emitted on the :class:`.MetaData`.
fixes #3124
|
|
|
|
| |
to get all flake8 passing
|
|
|
|
|
|
|
|
| |
MySQLconnector. This was set at True for some reason. The "buffered"
flag unfortunately must stay at True as MySQLconnector does not allow
a cursor to be closed unless all results are fully fetched. fixes #2515
- lots of MySQL tests seemed to not be hitting all backends, so we should
be getting some mysqlconnector failures now
|
|
|
|
| |
implements PG's to_tsquery('regconfig', 'arg') pattern. fixes #3078
|
|\
| |
| | |
Postgres 9.4 Jsonb support
|
| |
| |
| |
| | |
need to see if equality already works.
|
| |
| |
| |
| |
| |
| | |
from hstore that don't apply.
Add tests for ? and @> operators.
|
| | |
|
| |
| |
| |
| |
| | |
datatype - this does not add any of the additional support for
querying/indexing yet.
|
|\ \
| | |
| | | |
Fixed support for multivalue inserts for MS SQL 2008
|
| | |
| | |
| | |
| | | |
supported.
|
| | |
| | |
| | |
| | | |
the pg8000 DBAPI's encoding behavior, fixes #3112.
|
| | |
| | |
| | |
| | | |
fixes #3110
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
ProgrammingError, not OperationalError, in modern MySQL-Python versions;
all MySQL error codes that are tested for "is disconnect" are now
checked within OperationalError and ProgrammingError regardless.
fixes #3101
|
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|/
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
- restore mysqldb fully within dialects/mysql/, it's no longer a connector.
fixes #2984
|
| |
|
|\ |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|