Michael Trier c81c7ff3d5 Modifications to allow the backends to control the behavior of an empty insert. If supports_empty_insert is True then the backend specifically supports the 'insert into t1 () values ()' syntax. If supports_default_values is True then the backend supports the 'insert into t1 default values' syntax. If both are false then the backend has no support for empty inserts at all and an exception gets raised. Changes here are careful to not change current behavior except where the current behavior was failing to begin with.

2008-10-20 15:21:00 +00:00

..

__init__.py

- The 'length' argument to all Numeric types has been renamed

2008-08-24 19:52:54 +00:00

access.py

- Temporarily rolled back the "ORDER BY" enhancement

2008-08-06 15:46:31 +00:00

firebird.py

- The 'length' argument to all Numeric types has been renamed

2008-08-24 19:52:54 +00:00

information_schema.py

Columns now have default= and server_default=. PassiveDefault fades away.

2008-05-14 19:49:40 +00:00

informix.py

- 0.5.0rc3, doh

2008-10-18 18:14:06 +00:00

maxdb.py

- "not equals" comparisons of simple many-to-one relation

2008-10-18 17:34:52 +00:00

mssql.py

Modifications to allow the backends to control the behavior of an empty insert. If supports_empty_insert is True then the backend specifically supports the 'insert into t1 () values ()' syntax. If supports_default_values is True then the backend supports the 'insert into t1 default values' syntax. If both are false then the backend has no support for empty inserts at all and an exception gets raised. Changes here are careful to not change current behavior except where the current behavior was failing to begin with.

2008-10-20 15:21:00 +00:00

mxODBC.py

r4695 merged to trunk; trunk now becomes 0.5.

2008-05-09 16:34:10 +00:00

mysql.py

Fixed mysql TEMPORARY table reflection.

2008-09-27 18:26:53 +00:00

oracle.py

- 0.5.0rc3, doh

2008-10-18 18:14:06 +00:00

postgres.py

Modifications to allow the backends to control the behavior of an empty insert. If supports_empty_insert is True then the backend specifically supports the 'insert into t1 () values ()' syntax. If supports_default_values is True then the backend supports the 'insert into t1 default values' syntax. If both are false then the backend has no support for empty inserts at all and an exception gets raised. Changes here are careful to not change current behavior except where the current behavior was failing to begin with.

2008-10-20 15:21:00 +00:00

sqlite.py

Modifications to allow the backends to control the behavior of an empty insert. If supports_empty_insert is True then the backend specifically supports the 'insert into t1 () values ()' syntax. If supports_default_values is True then the backend supports the 'insert into t1 default values' syntax. If both are false then the backend has no support for empty inserts at all and an exception gets raised. Changes here are careful to not change current behavior except where the current behavior was failing to begin with.

2008-10-20 15:21:00 +00:00

sybase.py

- "not equals" comparisons of simple many-to-one relation

2008-10-18 17:34:52 +00:00