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

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

- 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

- ensure literal_binds works with LIMIT clause, FOR UPDATE

2014-09-03T23:42:38+00:00

- The hostname-based connection format for SQL Server when using

2014-09-03T14:31:29+00:00

pyodbc will no longer specify a default "driver name", and a warning
is emitted if this is missing.  The optimal driver name for SQL Server
changes frequently and is per-platform, so hostname based connections
need to specify this. DSN-based connections are preferred.
fixes #3182

- An adjustment to table/index reflection such that if an index

2014-09-02T18:18:09+00:00

reports a column that isn't found to be present in the table,
a warning is emitted and the column is skipped.  This can occur
for some special system column situations as has been observed
with Oracle. fixes #3180

- reorganize

2014-09-02T00:31:00+00:00

- The :func:`~.expression.column` and :func:`~.expression.table`

2014-09-02T00:19:54+00:00

constructs are now importable from the "from sqlalchemy" namespace,
just like every other Core construct.
- The implicit conversion of strings to :func:`.text` constructs
when passed to most builder methods of :func:`.select` as
well as :class:`.Query` now emits a warning with just the
plain string sent.   The textual conversion still proceeds normally,
however.  The only method that accepts a string without a warning
are the "label reference" methods like order_by(), group_by();
these functions will now at compile time attempt to resolve a single
string argument to a column or label expression present in the
selectable; if none is located, the expression still renders, but
you get the warning again. The rationale here is that the implicit
conversion from string to text is more unexpected than not these days,
and it is better that the user send more direction to the Core / ORM
when passing a raw string as to what direction should be taken.
Core/ORM tutorials have been updated to go more in depth as to how text
is handled.
fixes #2992

- more updates to text docs, literal_column, column etc. in prep

2014-09-01T21:20:49+00:00

for ticket 2992.

- walk back these literal SQL lectures into something much more succinct.

2014-09-01T00:26:40+00:00

the ORM one in particular was really long winded and I don't really care if people
use text() anyway, they'll figure it out ;)

- A new style of warning can be emitted which will "filter" up to

2014-08-31T19:22:00+00:00

N occurrences of a parameterized string.   This allows parameterized
warnings that can refer to their arguments to be delivered a fixed
number of times until allowing Python warning filters to squelch them,
and prevents memory from growing unbounded within Python's
warning registries.
fixes #3178