As an addition to the previous mail: I am going full circles here.
If I add:
```
def get_insert_default(self, column):
if (column.primary_key and column is
column.table._autoincrement_column and
column.default is None or
(isinstance(column.default, sche
On Sunday, January 7, 2018 at 12:07:13 AM UTC+1, Mike Bayer wrote:
>
> 1. will you always use sequences?
>
No, my dialect tries to use sequences only when the are explicitly
specified, otherwise it tries to use SERIAL. So:
Column('id', Integer, Sequence('some_id_seq'), primary_key=True) uses
On Sat, Jan 6, 2018 at 3:31 PM, Florian Apolloner wrote:
>
>
> On Saturday, January 6, 2018 at 8:53:41 PM UTC+1, Mike Bayer wrote:
>>
>> Can you confirm the exact sql and parameters you are seeing? SQLAlchemy
>> never sends NULL for an auto increment id column, it omits it from the
>> statement s
On Saturday, January 6, 2018 at 8:53:41 PM UTC+1, Mike Bayer wrote:
>
> Can you confirm the exact sql and parameters you are seeing? SQLAlchemy
> never sends NULL for an auto increment id column, it omits it from the
> statement so that the default takes place, which I assume is what you mean
Can you confirm the exact sql and parameters you are seeing? SQLAlchemy
never sends NULL for an auto increment id column, it omits it from the
statement so that the default takes place, which I assume is what you mean
by "leave it out".
On Jan 6, 2018 1:52 PM, "Florian Apolloner" wrote:
> Hi,
>
Hi,
Informix mostly follows the Postgresql behavior when it comes to SERIAL
columns with one notable exception: I have to specify 0 (0 as int, not
NULL) for a SERIAL column on insert or leave it out.
Code like:
```
Table('date_table', metadata,
Column('id', Integer, primar
