delta/python-packages/sqlalchemy.git/doc, branch pr/135

Updated documenation for engines.rst

2014-09-14T04:25:41+00:00

Clarified connecting to absolute path for sqlite using Windows.

- Fixed warning that would emit when a complex self-referential

2014-09-11T15:51:44+00:00

primaryjoin contained functions, while at the same time remote_side
was specified; the warning would suggest setting "remote side".
It now only emits if remote_side isn't present.
fixes #3194

- Fixed bug in ordering list where the order of items would be

2014-09-10T18:14:50+00:00

thrown off during a collection replace event, if the
reorder_on_append flag were set to True.  The fix ensures that the
ordering list only impacts the list that is explicitly associated
with the object.
fixes #3191

- for whatever reason, Insert.values() with multi values wasn't

2014-09-09T22:59:59+00:00

in the 0.8 migration, so let's just add that

- Added new event handlers :meth:`.AttributeEvents.init_collection`

2014-09-08T00:28:19+00:00

and :meth:`.AttributeEvents.dispose_collection`, which track when
a collection is first associated with an instance and when it is
replaced.  These handlers supersede the :meth:`.collection.linker`
annotation. The old hook remains supported through an event adapter.

- mako_layout isn't used, remove it

2014-09-07T22:10:40+00:00

- to check for epub look at "builder"

Merge pull request #133 from hiaselhans/doc_epub

2014-09-07T21:38:05+00:00

Docs: use layout.mako only when mako_layout=='html'

Docs: use the base layout when mako_layout=='epub'

2014-09-07T20:55:05+00:00

  - https://readthedocs.org/projects/sqlalchemy/downloads/epub/latest/ renders with the full template which is unreadable on e-readers
  - in the makefile the template-variable mako_layout is set for target: epub which makes mako use only the base layout.
  - this is the more elegant solution as proposed to #133

- changelog and migration for #3188, #3148.

2014-09-07T19:23:24+00:00

fixes #3188
fixes #3148

- MySQL boolean symbols "true", "false" work again. 0.9's change

2014-09-05T20:44:42+00:00

in :ticket:`2682` disallowed the MySQL dialect from making use of the
"true" and "false" symbols in the context of "IS" / "IS NOT", but
MySQL supports this syntax even though it has no boolean type.
MySQL remains "non native boolean", but the :func:`.true`
and :func:`.false` symbols again produce the
keywords "true" and "false", so that an expression like
``column.is_(true())`` again works on MySQL.
fixes #3186