summaryrefslogtreecommitdiff
path: root/lib
Commit message (Collapse)AuthorAgeFilesLines
* sqlalchemy/dialects/postgresql/pgjson:pr/50nathan2013-12-111-7/+14
| | | | - Updated documentation for JSON class
* sqlalchemy/dialects/postgresql/pgjson:nathan2013-12-111-2/+14
| | | | | - Added support for additional operators - Made return as json default (rather than text)
* sqlalchemy/dialects/postgresql/psycopg2:nathan2013-12-101-2/+0
| | | | - Removed unneeded import of psycopg2.extensions
* sqlalchemy/dialects/postgresql/pgjson:nathan2013-12-102-2/+19
| | | | | | | | | | | | - 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
* Merge branch 'rel_0_9' of https://github.com/nathan-rice/sqlalchemy into rel_0_9nathan2013-12-092-6/+8
|\
| * - The precedence rules for the :meth:`.ColumnOperators.collate` operatorMike Bayer2013-12-051-1/+5
| | | | | | | | | | | | | | | | | | | | | | have been modified, such that the COLLATE operator is now of lower precedence than the comparison operators. This has the effect that a COLLATE applied to a comparison will not render parenthesis around the comparison, which is not parsed by backends such as MSSQL. The change is backwards incompatible for those setups that were working around the issue by applying :meth:`.Operators.collate` to an individual element of the comparison expression, rather than the comparison expression as a whole. [ticket:2879]
| * Fix MSSQL dialects visit_drop_index to use the correct DDLdonkopotamus2013-12-051-5/+3
| |
* | sqlalchemy/dialects/postgresql/__init__.py:nathan2013-12-093-1/+114
|/ | | | | | | | | | - 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.
* - reflection of unique constraints backported to 0.8.4 [ticket:1443]Mike Bayer2013-12-031-1/+1
|
* - The :class:`.DeferredReflection` class has been enhanced to provideMike Bayer2013-12-032-38/+75
| | | | | | | | | | | | | | | | automatic reflection support for the "secondary" table referred to by a :func:`.relationship`. "secondary", when specified either as a string table name, or as a :class:`.Table` object with only a name and :class:`.MetaData` object will also be included in the reflection process when :meth:`.DeferredReflection.prepare` is called. [ticket:2865] - clsregistry._resolver() now uses a stateful _class_resolver() class in order to handle the work of mapping strings to objects. This is to provide for simpler extensibility, namely a ._resolvers collection of ad-hoc name resolution functions; the DeferredReflection class adds its own resolver here in order to handle relationship(secondary) names which generate new Table objects.
* - Added ORA-02396 "maximum idle time" error code to list ofMike Bayer2013-12-031-1/+2
| | | | "is disconnect" codes with cx_oracle. [ticket:2864]
* - Added new argument ``include_backrefs=True`` to theMike Bayer2013-12-023-12/+45
| | | | | | | :func:`.validates` function; when set to False, a validation event will not be triggered if the event was initated as a backref to an attribute operation from the other side. [ticket:1535] - break out validation tests into an updated module test_validators
* - changelogMike Bayer2013-11-301-7/+8
| | | | - put list.clear() instrumentation under "if not py2k"
* Merge branch 'orm-collections-list-clear' of ↵Mike Bayer2013-11-301-0/+8
|\ | | | | | | github.com:schettino72/sqlalchemy into list_clear
| * orm.collection, list.clear(). remove 'before_delete()', added unit-test.pr/40schettino722013-11-251-1/+0
| |
| * Add support for python3.3 list.clear() on orm.collectionsschettino722013-11-061-0/+9
| |
* | - re-document synonyms and remove warnings about "superseded"; synonymsMike Bayer2013-11-301-33/+50
| | | | | | | | | | are still useful, just include notes that for more complex descriptor operations, hybrids are probably preferable
* | - Fixed bug where values within an ENUM weren't escaped for singleMike Bayer2013-11-301-1/+3
| | | | | | | | | | quote signs. Note that this is backwards-incompatible for existing workarounds that manually escape the single quotes. [ticket:2878]
* | convert to a list here for py3kMike Bayer2013-11-291-1/+1
| |
* | - add support for bindparam() called from AsFromTextMike Bayer2013-11-292-13/+20
| | | | | | | | | | - get PG dialect to work around "no nonexistent binds" rule for now, though we might want to reconsider this behavior
* | Fixed bug where in Py2K a unicode literal would not be acceptedMike Bayer2013-11-291-1/+1
| | | | | | | | | | as the string name of a class or other argument within declarative using :func:`.relationship`.
* | - reduce verbiage in mutation.py regarding legacy style, place under ↵Mike Bayer2013-11-291-7/+3
| | | | | | | | versionadded
* | Fixed a syntax error in example code.Hyunjun Kim2013-11-291-1/+1
| |
* | Merge pull request #45 from timka/patch-1mike bayer2013-11-291-1/+1
|\ \ | | | | | | Fix sessionmaker.__repr__
| * | Fix sessionmaker.__repr__pr/45Timur2013-11-161-1/+1
| | | | | | | | | A comma separating 'class_' from the other args. It's still there even when kw is empty, which is syntactically correct.
* | | Merge pull request #46 from vrajmohan/mastermike bayer2013-11-2912-29/+29
|\ \ \ | | | | | | | | More fixes for cross references and reducing warnings (3rd wave)
| * | | Fix cross referencespr/46Vraj Mohan2013-11-175-9/+9
| | | |
| * | | Generate API and resolve cross referencesVraj Mohan2013-11-172-5/+5
| | | |
| * | | Fix cross referencesVraj Mohan2013-11-174-13/+13
| | | |
| * | | Add API generation to resolve cross referencesVraj Mohan2013-11-171-1/+1
| | | |
| * | | Remove reference to defunct classVraj Mohan2013-11-171-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | We should probably reword this entirely as, IMHO, this should be in the changelog and not in the doc proper (which should only describe the current state of affairs).
* | | | more fixMike Bayer2013-11-291-1/+1
| | | |
* | | | fixMike Bayer2013-11-291-1/+1
| | | |
* | | | make generativeselect availableMike Bayer2013-11-291-1/+1
| | | |
* | | | - New improvements to the :func:`.text` construct, includingMike Bayer2013-11-294-193/+482
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | more flexible ways to set up bound parameters and return types; in particular, a :func:`.text` can now be turned into a full FROM-object, embeddable in other statements as an alias or CTE using the new method :meth:`.TextClause.columns`. [ticket:2877]
* | | | - repair the "lockmode" functionality of load_on_ident(). slightly problematicMike Bayer2013-11-281-4/+9
| | | | | | | | | | | | | | | | here is that "lockmode" is also public in Session.refresh().
* | | | - add support for specifying tables or entities for "of"Mike Bayer2013-11-284-67/+114
| | | | | | | | | | | | | | | | | | | | - implement Query with_for_update() - rework docs and tests
* | | | - fix up rendering of "of"Mike Bayer2013-11-285-17/+25
| | | | | | | | | | | | | | | | | | | | | | | | - move out tests, dialect specific out of compiler, compiler tests use new API, legacy API tests in test_selecatble - add support for adaptation of ForUpdateArg, alias support in compilers
* | | | - work in progress, will squashMike Bayer2013-11-286-137/+163
| | | |
* | | | Merge branch 'for_update_of' of github.com:mlassnig/sqlalchemy into ↵Mike Bayer2013-11-286-42/+156
|\ \ \ \ | | | | | | | | | | | | | | | for_update_of
| * | | | added LockmodeArgspr/42Mario Lassnig2013-11-286-70/+135
| | | | |
| * | | | added ORM supportMario Lassnig2013-11-144-16/+48
| | | | |
| * | | | add psql FOR UPDATE OF functionalityMario Lassnig2013-11-124-1/+18
| | |_|/ | |/| |
* | | | - add more explicit docs for relationship mixin, [ticket:2876]Mike Bayer2013-11-271-4/+50
| | | |
* | | | - the wrapped memoized_property here was not working, as the attribute nameMike Bayer2013-11-262-12/+25
| | | | | | | | | | | | | | | | didn't match. use straight memoized_props here for now, add a perf test to check it
* | | | - adjustment, the spec says: "Within the user and password field, any ":",Mike Bayer2013-11-253-5/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | "@", or "/" must be encoded." - so re-apply encoding to both password and username, don't encode spaces as plus signs, don't encode any chars outside of :, @, / on stringification - but we still parse for any %XX character (is that right?)
* | | | - The :func:`.create_engine` routine and the relatedMike Bayer2013-11-241-7/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | :func:`.make_url` function **no longer URL encode the password**. Database passwords that include characters like spaces, plus signs and anything else should now represent these characters directly, without any URL escaping. [ticket:2873]
* | | | pg8000 fix for decimal return scaleMike Bayer2013-11-231-1/+2
| | | |
* | | | - evaulate decimal_return_scale statelessly. Don't re-assign to ↵Mike Bayer2013-11-234-12/+16
| | | | | | | | | | | | | | | | | | | | | | | | self.decimal_return_scale so that __repr__() is maintained (for alembic tests)
* | | | - Some refinements to the :class:`.AliasedClass` construct with regardsMike Bayer2013-11-232-15/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | to descriptors, like hybrids, synonyms, composites, user-defined descriptors, etc. The attribute adaptation which goes on has been made more robust, such that if a descriptor returns another instrumented attribute, rather than a compound SQL expression element, the operation will still proceed. Addtionally, the "adapted" operator will retain its class; previously, a change in class from ``InstrumentedAttribute`` to ``QueryableAttribute`` (a superclass) would interact with Python's operator system such that an expression like ``aliased(MyClass.x) > MyClass.x`` would reverse itself to read ``myclass.x < myclass_1.x``. The adapted attribute will also refer to the new :class:`.AliasedClass` as its parent which was not always the case before. [ticket:2872]
View Lorry Controller Status