| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
| |
This makes the code block more consistent with the preceding one and also prevents the variable from being colored as a builtin (which `object` is) during syntax highlighting.
|
|
|
|
|
|
|
|
|
| |
the indexing. this is for more natural operation.
- also add cast() to the JSON expression to complement astext. This integrates
the CAST call which will be needed frequently. Part of [ticket:2687].
- it's a little unclear how more advanced unicode attribute-access is going to go,
some quick attempts at testing yielded strange error messages from psycopg2.
- do other cross linking as mentioned in [ticket:2687].
|
|
|
|
|
|
|
| |
:class:`.Column` is mapped multiple times under different properties
(which typically should be a :func:`.synonym` instead) or if two
or more :class:`.Column` objects are given the same name, raising
a warning if this condition is detected. [ticket:2828]
|
|
|
|
|
|
|
|
|
| |
to query from the ``rdb$relations`` view instead of the
``rdb$relation_fields`` and ``rdb$view_relations`` views.
Variants of both the old and new queries are mentioned on many
FAQ and blogs, however the new queries are taken straight from
the "Firebird FAQ" which appears to be the most official source
of info. [ticket:2898]
|
| |
|
|
|
|
| |
underscore. Courtesy Treeve Jelbert. [ticket:2897]
|
|
|
|
|
|
| |
that the lists
of each can be reflected independently. Testing [ticket:2898] at the moment.
|
|
|
|
|
| |
index were not sorted correctly; they are now sorted
in order of RDB$FIELD_POSITION.
|
|
|
|
|
|
| |
work with Firebird dialects; previously the decimal conversion was
not occurring.
- scale back some firebird FP numeric tests
|
| |
|
| |
|
|\
| |
| | |
Remove terminated connections from the pool.
|
| |
| |
| |
| |
| |
| | |
In pymssql, if you terminate a long running query manually
it will give you a connection reset by peer message, but this
connection remains in the pool and will be re-used.
|
| |
| |
| |
| |
| | |
to use a named def instead of a lambda. this so that TypeError on wrong
arguments are more legible. [ticket:2884]
|
| |
| |
| |
| | |
[ticket:2852]
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
yet the column is not the "auto increment" column, either because
it has a foreign key constraint or ``autoincrement=False`` set,
would attempt to fire the Sequence on INSERT for backends that don't
support sequences, when presented with an INSERT missing the primary
key value. This would take place on non-sequence backends like
SQLite, MySQL. [ticket:2896]
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
of the given names would not be taken into account when generating
the INSERT statement, thus producing a mismatch versus the column
names in the given SELECT statement. Also noted that
:meth:`.Insert.from_select` implies that Python-side insert defaults
cannot be used, since the statement has no VALUES clause. [ticket:2895]
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
``__repr__()``, particularly with regards to the MySQL integer/numeric/
character types which feature a wide variety of keyword arguments.
The ``__repr__()`` is important for use with Alembic autogenerate
for when Python code is rendered in a migration script.
[ticket:2893]
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
compatible with psycopg2's per-connection/cursor approach. add round trip tests for
both native and non-native.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
will now apply the given type to the given literal value on the
bind parameter side according
to the type given to the cast. This essentially replaces what would
normally be the detected type of the literal value. This only
takes effect if the auto-detected type of the literal value is either
"nulltype" (e.g. couldn't detect)
or a type that is of the same "affinity" as the cast type.
The net change here is that the :func:`.cast` function includes more
of the functionality already present in the :func:`.type_coerce` function.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- add support for "standalone" JSON objects; this involves getting CAST
to upgrade the given type of a bound parameter. should add a core-only test
for this.
- add tests for "standalone" json round trips both with and without unicode
- add mechanism by which we remove psycopg2's "json" handler in order to get
the effect of using our non-native result handlers
|
| |
| |
| |
| | |
__only_on__ attribute
|
|\ \ |
|
| | |
| | |
| | |
| | | |
- Updated documentation for JSON class
|
| | |
| | |
| | |
| | |
| | | |
- Added support for additional operators
- Made return as json default (rather than text)
|
| | |
| | |
| | |
| | | |
- Removed unneeded import of psycopg2.extensions
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- Fixed reference to HSTORE
- Corrected spelling of SQLAlchemy
sqlalchemy/dialects/postgresql/psycopg2:
- Added psycopg2 specific wrapper type for JSON which uses inherent json deserialization facilities
- Added code to detect and utilize the JSON wrapper if psycopg2 >= 2.5
test/dialect/postgresql/test_types:
- removed reference to use_native_hstore
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- Added import references to JSON class
sqlalchemy/dialects/postgresql/base.py:
- Added visitor method for JSON class
sqlalchemy/dialects/postgresql/pgjson (new):
- JSON class, supports automatic serialization and deserialization of json data, as well as basic json operators.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
backwards compatibility. A note about backslashing escapes is added.
Because the Text() construct now supports bind params better, the example
given in the code raises an exception now, so that should cover us.
The exception itself has been enhanced to include the key name of the
bound param. We're backporting this to 0.8 but 0.8 doesn't have the
text->bind behavior that raises.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
the query runs after the loading process has begun; this is so that
the subqueryload takes precedence over other loaders that may be
hitting the same attribute due to other eager/noload situations
at the wrong time. [ticket:2887]
|
| | | |
| | | |
| | | |
| | | | |
- add session object states to the glossary
|
| |_|/
|/| |
| | |
| | |
| | |
| | |
| | | |
select/alias on the base, where the PK columns were also not same
named; the persistence system would fail to copy primary key values
from the base table to the inherited table upon INSERT.
[ticket:2885]
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
doing the isinstance() check - currently used only by psycopg2 + native enum + py2k.
- didn't realize psycopg2 had UNICODEARRAY extension all this time; replace _PGArray
with just using UNICODEARRAY instead.
- replace unnecessary/inconsistent __import__ in _isolation_lookup.
|
| | |
| | |
| | |
| | | |
not be superseded. both have a potential use.
|
| | |
| | |
| | |
| | | |
composites to many-to-ones now also
|
| | |
| | |
| | |
| | |
| | |
| | | |
columns/attribute (names) passed don't resolve to a Column or mapped
attribute (such as an erroneous tuple); previously raised an unbound
local. [ticket:2889]
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
doesn't resolve to a class or mapper has been corrected to work
the same way as when a non-string arg is received, which indicates
the name of the relationship which had the configurational error.
[ticket:2888]
|
| | |
| | |
| | |
| | |
| | |
| | | |
of things
that can definitely people should be more focused.
|