auto commit by copy to link target

• Files Changed
• Browse Source

- update to version 1.2.8:
  * orm
    + [orm] [bug] Fixed regression in 1.2.7 caused by #4228, which 
      itself was fixing a 1.2-level regression, where the query_cls
      callable passed to a Session was assumed to be a subclass of 
      Query with class method availability, as opposed to an 
      arbitrary callable. In particular, the dogpile caching example 
      illustrates query_cls as a function and not a Query subclass. 
      References: #4256
    + [orm] [bug] Fixed a long-standing regression that occurred in 
      version 1.0, which prevented the use of a custom MapperOption 
      that alters the _params of a Query object for a lazy load, 
      since the lazy loader itself would overwrite those parameters. 
      This applies to the “temporal range” example on the wiki. Note 
      however that the Query.populate_existing() method is now 
      required in order to rewrite the mapper options associated with 
      an object already loaded in the identity map.
      As part of this change, a custom defined MapperOption will now 
      cause lazy loaders related to the target object to use a non-
      baked query by default unless the 
      MapperOption._generate_cache_key() method is implemented. In 
      particular, this repairs one regression which occured when 
      using the dogpile.cache “advanced” example, which was not 
      returning cached results and instead emitting SQL due to an 
      incompatibility with the baked query loader; with the change, 
      the RelationshipCache option included for many releases in the 
      dogpile example will disable the “baked” query altogether. Note 
      that the dogpile example is also modernized to avoid both of 
      these issues as part of issue #4258.  References: #4128
    + [orm] [bug] Fixed bug where the new

• Files Changed
• Browse Source

undeleted via osc

• Files Changed
• Browse Source

- Update to version 0.8.3:
  + See http://docs.sqlalchemy.org/en/latest/changelog/changelog_08.html#change-0.8.3
- Drop outdated patches
  + SQLAlchemy-0.7.10-SLES-drop-failing-tests.patch
  + sqlalchemy-0.7-logging.patch

• Files Changed
• Browse Source

- merge with factory

- Require python-setuptools instead of distribute (upstreams merged)
--------------------------------------------------------------------
------------------------------------------------------------------

• Files Changed
• Browse Source

- adjust SLES-drop-failing-tests.patch for 0.8.2

• Files Changed
• Browse Source

- update to 0.8.2
  changes are too many to be listed here in a sane way, see:
  http://docs.sqlalchemy.org/en/rel_0_8/changelog/changelog_08.html

• Files Changed
• Browse Source

auto commit by copy to link target

• Files Changed
• Browse Source

- apply patch to fix TypeError, when running python setup.py test

• Files Changed
• Browse Source

apply a patch, that fixed the test rig

• Files Changed
• Browse Source

add build dep python-sqlite in order to get the tests running,
but don't bail out on test failures

• Files Changed
• Browse Source

• Files Changed
• Browse Source

- do not require python-pysqlite package.
- update to 0.7.9:
  *orm
  - [bug] Fixed bug mostly local to new AbstractConcreteBase helper
    where the "type" attribute from the superclass would not be overridden
    on the subclass to produce the "reserved for base" error message,
    instead placing a do-nothing attribute there. This was inconsistent
    vs. using ConcreteBase as well as all the behavior of classical
    concrete mappings, where the "type" column from the polymorphic base
    would be explicitly disabled on subclasses, unless overridden
    explicitly.
  - [bug] A warning is emitted when lazy='dynamic' is combined with
    uselist=False. This is an exception raise in 0.8.
  - [bug] Fixed bug whereby user error in related-object assignment could
    cause recursion overflow if the assignment triggered a backref of the
    same name as a bi-directional attribute on the incorrect class to the
    same target. An informative error is raised now.
  - [bug] Fixed bug where incorrect type information would be passed when
    the ORM would bind the "version" column, when using the "version"
    feature. Tests courtesy Daniel Miller. [ticket:2539]
  - [bug] Extra logic has been added to the "flush" that occurs within
    Session.commit(), such that the extra state added by an after_flush()
    or after_flush_postexec() hook is also flushed in a subsequent flush,
    before the "commit" completes. Subsequent calls to flush() will
    continue until the after_flush hooks stop adding new state. An
    "overflow" counter of 100 is also in place, in the event of a broken
    after_flush() hook adding new content each time.  [ticket:2566] 
  *engine
  - [feature] Dramatic improvement in memory usage of the event system;
    instance-level collections are no longer created for a particular type of

• Files Changed
• Browse Source

• Files Changed
• Browse Source

• Browse Source