summaryrefslogtreecommitdiff
path: root/doc
Commit message (Collapse)AuthorAgeFilesLines
...
* - changelog for pullreq github 57Mike Bayer2014-01-121-0/+7
|
* - pullreq github 55 is in the wrong changelog! 0.9.2...Mike Bayer2014-01-121-2/+5
|
* new changelogMike Bayer2014-01-111-1/+1
|
* changelog for pullreq github:55pullreq55Mike Bayer2014-01-091-0/+11
|
* - fixesMike Bayer2014-01-081-4/+4
|
* - add more critical behavioral change for [ticket:2804]Mike Bayer2014-01-081-1/+49
|
* - 0.9.1rel_0_9_1Mike Bayer2014-01-052-2/+3
|
* fix the changelog mergeMike Bayer2014-01-051-3/+2
|
* - happy new yearMike Bayer2014-01-052-3/+3
|
* - docs + testsMike Bayer2014-01-051-0/+22
|
* Merge branch 'automap'Mike Bayer2014-01-055-15/+118
|\ | | | | | | | | Conflicts: doc/build/changelog/changelog_09.rst
| * - many-to-many supportMike Bayer2014-01-054-2/+80
| | | | | | | | | | - tests - full documentation, changelog, new in 0.9 announcement
| * - fix some docstring stuffMike Bayer2014-01-051-13/+19
| |
| * - conjunctions like and_() and or_() can now accept generators as arguments.Mike Bayer2014-01-051-0/+11
| |
| * - The :paramref:`.Table.extend_existing` and :paramref:`.Table.autoload_replace`Mike Bayer2014-01-042-1/+8
| | | | | | | | | | | | parameters are now available on the :meth:`.MetaData.reflect` method. - starting to use paramref and need newer paramlinks version.
* | - Fixed regression where using a ``functools.partial()`` with the eventMike Bayer2014-01-041-0/+13
|/ | | | | | | | | | | system would cause a recursion overflow due to usage of inspect.getargspec() on it in order to detect a legacy calling signature for certain events, and apparently there's no way to do this with a partial object. Instead we skip the legacy check and assume the modern style; the check itself now only occurs for the SessionEvents.after_bulk_update and SessionEvents.after_bulk_delete events. Those two events will require the new signature style if assigned to a "partial" event listener. [ticket:2905]
* - Fixed an extremely unlikely memory issue where when usingMike Bayer2014-01-031-0/+12
| | | | | | | | | | :class:`.DeferredReflection` to define classes pending for reflection, if some subset of those classes were discarded before the :meth:`.DeferredReflection.prepare` method were called to reflect and map the class, a strong reference to the class would remain held within the declarative internals. This internal collection of "classes to map" now uses weak references against the classes themselves.
* Merged in davidszotten/sqlalchemy/doc_typo (pull request #10) Mike Bayer2014-01-021-1/+1
|\ | | | | typo in changelog
| * typo in changelogDavid Szotten2014-01-011-1/+1
| |
* | - changelog for pullreq 9 from bitbucketMike Bayer2014-01-021-0/+8
| |
* | - Fixed regression where we don't check the given name against theMike Bayer2014-01-021-0/+9
| | | | | | | | | | | | correct string class when setting up a backref based on a name, therefore causing the error "too many values to unpack". This was related to the Py3k conversion. [ticket:2901]
* | - A quasi-regression where apparently in 0.8 you can set a class-levelMike Bayer2014-01-021-0/+14
| | | | | | | | | | | | | | | | | | | | | | attribute on declarative to simply refer directly to an :class:`.InstrumentedAttribute` on a superclass or on the class itself, and it acts more or less like a synonym; in 0.9, this fails to set up enough bookkeeping to keep up with the more liberalized backref logic from :ticket:`2789`. Even though this use case was never directly considered, it is now detected by declarative at the "setattr()" level as well as when setting up a subclass, and the mirrored/renamed attribute is now set up as a :func:`.synonym` instead. [ticket:2900]
* | - Fixed regression where we apparently still create an implicitMike Bayer2014-01-021-0/+15
|/ | | | | | | | | | alias when saying query(B).join(B.cs), where "C" is a joined inh class; however, this implicit alias was created only considering the immediate left side, and not a longer chain of joins along different joined-inh subclasses of the same base. As long as we're still implicitly aliasing in this case, the behavior is dialed back a bit so that it will alias the right side in a wider variety of cases. [ticket:2903]
* - 0.9.0 release daterel_0_9_0Mike Bayer2013-12-302-2/+3
|
* - call it 0.9.0Mike Bayer2013-12-303-24/+24
|
* sphinx paramlinks 0.1.8Mike Bayer2013-12-301-1/+1
|
* - use 0.1.7 at leastMike Bayer2013-12-301-1/+1
|
* - try out paramlinksMike Bayer2013-12-302-0/+2
|
* - apply a similar fix for floats to mssql+pyodbc as we did to firebirdMike Bayer2013-12-281-3/+3
| | | | | - wrangle through osx+pyodbc+freetds to get at least test_suite to pass again with mssql+pyodbc. invovled adding some silly requirements
* - adjust the behavior of cast() to only provide a type for the bindparam()Mike Bayer2013-12-281-8/+5
| | | | | if we are coercing straight from string. [ticket:2899] - rework the tests here to be individual
* session docs: Change `object` to `someobject`pr/54Ben Alpert2013-12-271-1/+1
| | | 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.
* - rework the JSON expression system so that "astext" is called *after*Mike Bayer2013-12-272-0/+16
| | | | | | | | | 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].
* - Declarative does an extra check to detect if the sameMike Bayer2013-12-271-0/+10
| | | | | | | :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]
* - Changed the queries used by Firebird to list table and view namesMike Bayer2013-12-271-0/+12
| | | | | | | | | 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]
* - The firebird dialect will quote identifiers which begin with anMike Bayer2013-12-271-0/+8
| | | | underscore. Courtesy Treeve Jelbert. [ticket:2897]
* - Fixed bug in Firebird index reflection where the columns within theMike Bayer2013-12-271-0/+8
| | | | | index were not sorted correctly; they are now sorted in order of RDB$FIELD_POSITION.
* - The "asdecimal" flag used with the :class:`.Float` type will nowMike Bayer2013-12-271-0/+8
| | | | | | work with Firebird dialects; previously the decimal conversion was not occurring. - scale back some firebird FP numeric tests
* changelog, will merge to 0.8Mike Bayer2013-12-271-0/+9
|
* - Fixed issue where a primary key column that has a Sequence on it,Mike Bayer2013-12-201-0/+13
| | | | | | | | | 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]
* - Fixed bug with :meth:`.Insert.from_select` method where the orderMike Bayer2013-12-191-0/+12
| | | | | | | | 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]
* - Improvements to the system by which SQL types generate withinMike Bayer2013-12-181-0/+10
| | | | | | | | ``__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]
* this is a github PRMike Bayer2013-12-171-1/+1
|
* add JSONMike Bayer2013-12-171-1/+3
|
* - changelogMike Bayer2013-12-171-0/+9
|
* - The :func:`.cast` function, when given a plain literal value,Mike Bayer2013-12-171-0/+14
| | | | | | | | | | | | 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.
* - for [ticket:2651], leaving CheckConstraint alone, preferring to keepMike Bayer2013-12-161-0/+8
| | | | | | | | | 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.
* - An adjustment to the :func:`.subqueryload` strategy which ensures thatMike Bayer2013-12-161-0/+11
| | | | | | | 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]
* - fix up the FAQ regarding the "foo_id" issueMike Bayer2013-12-162-18/+110
| | | | - add session object states to the glossary
* - Fixed bug when using joined table inheritance from a table to aMike Bayer2013-12-161-0/+10
| | | | | | | 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]
* - add "force_nocheck" as a way to turn on unicode=force without evenMike Bayer2013-12-151-0/+7
| | | | | | | 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.
View Lorry Controller Status