delta/python-packages/sqlalchemy.git, branch pr/133 github.com: zzzeek/sqlalchemy.git Docs: use the base layout when mako_layout=='epub' 2014-09-07T20:55:05+00:00 hiaselhans simon@booya.at 2014-09-06T11:32:58+00:00 a8ef876f6c30273da55c727c315f16f01ffc3abc - 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 
  - 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
- omit MySQL index flavor if its None 2014-09-05T21:02:33+00:00 Mike Bayer mike_mp@zzzcomputing.com 2014-09-05T21:02:33+00:00 6844f8db74ab2ba5df98ba285be34a2534a88b5b 






- MySQL boolean symbols "true", "false" work again.  0.9's change
2014-09-05T20:44:42+00:00

Mike Bayer
mike_mp@zzzcomputing.com

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

7b766591b05ceeb9c47588d6326a6be56a230594

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





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







- delete the file first here so this is deterministic
2014-09-05T20:28:32+00:00

Mike Bayer
mike_mp@zzzcomputing.com

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

583287259fbb6d143696b418756ed68e6110cd2d












- tiny refactors #1-#5
2014-09-05T20:28:20+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2014-09-05T18:50:21+00:00

356d6659b17d199c1a5ecc4241e7ee3edc6a754e












- ensure literal_binds works with LIMIT clause, FOR UPDATE
2014-09-03T23:42:38+00:00

Mike Bayer
mike_mp@zzzcomputing.com

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

2b10aa45a101acfcc6090a3801af998ef8fc1a2d












- The hostname-based connection format for SQL Server when using
2014-09-03T14:31:29+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2014-09-03T14:30:51+00:00

4399431b53e5d132672431205c654d7d6b32dd77

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





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







- default dialect, plus test against the default dialect...
2014-09-02T19:04:12+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2014-09-02T19:04:12+00:00

613d8ca0f84d3e92b35403eaba21824e72b8ada8












- An adjustment to table/index reflection such that if an index
2014-09-02T18:18:09+00:00

Mike Bayer
mike_mp@zzzcomputing.com

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

ec840a6eea05ac031a55d262dc370bed942b2212

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





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







default dialect
2014-09-02T17:39:16+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2014-09-02T17:39:16+00:00

9ee89dc88671a8c5d005c5baf3b2a7be58fee8ed