[sqlalchemy] Re: nullable=False by default

2008-07-07 Thread Kless
But I'm supposed that the generation function of autoincrement only works when the field is NULL or there is an integer, so this fails on fields with a string empty. On Jul 7, 8:06 am, Kless [EMAIL PROTECTED] wrote: Yes, I read it. The integer columns with the primary key flag set are not

[sqlalchemy] Re: nullable=False by default

2008-07-07 Thread Michael Bayer
On Jul 7, 2008, at 3:06 AM, Kless wrote: Yes, I read it. The integer columns with the primary key flag set are not being autoincremented, after of the Column subclass. what database ? Oracle and Firebird require a Sequence to be specified.

[sqlalchemy] Re: nullable=False by default

2008-07-07 Thread Michael Bayer
On Jul 7, 2008, at 3:10 AM, Kless wrote: But I'm supposed that the generation function of autoincrement only works when the field is NULL or there is an integer, so this fails on fields with a string empty. im not sure offhand what an empty string would produce since I'd have to check

[sqlalchemy] Re: nullable=False by default

2008-07-07 Thread Kless
Yes, it's SQLite. I use it into the development. On Jul 7, 4:06 pm, Michael Bayer [EMAIL PROTECTED] wrote: On Jul 7, 2008, at 3:10 AM, Kless wrote: But I'm supposed that the generation function of autoincrement only works when the field is NULL or there is an integer, so this fails on

[sqlalchemy] Re: nullable=False by default

2008-07-07 Thread Michael Bayer
then its probably inserting your blank string into the column. SQLA doesn't want to get too much in the way of the natural features of the database in use. On Jul 7, 2008, at 11:09 AM, Kless wrote: Yes, it's SQLite. I use it into the development. On Jul 7, 4:06 pm, Michael Bayer

[sqlalchemy] Re: nullable=False by default

2008-07-07 Thread Kless
You have reason. I checked it with MySQL and it works ok. So here I have a lesson learned: use the same RDBMS on developing. Thanks Michael. On Jul 7, 4:50 pm, Michael Bayer [EMAIL PROTECTED] wrote: then its probably inserting your blank string into the column.  SQLA   doesn't want to get too

[sqlalchemy] Re: nullable=False by default

2008-07-06 Thread Kless
And, why can I add 'default' -- def Column0(*a, **k): return Column(nullable=False, default='', *a, **k) -- it shows the next error: TypeError: _FigureVisitName object got multiple values for keyword argument 'default' On Jul 6, 7:53 pm, [EMAIL PROTECTED] wrote: u can

[sqlalchemy] Re: nullable=False by default

2008-07-06 Thread Kless
I'm using so: def Column0(*a, **k): return Column(nullable=False, default='', *a, **k) groups_table = Table('foo', metadata, Column0('id', Integer, primary_key=True), Column0('bar', Unicode(16)), ) Note: I'm using SA 0.5 beta. But well, that solved it. Thank you

[sqlalchemy] Re: nullable=False by default

2008-07-06 Thread Kless
I think that there is a bug. autoincrement doesn't works with *default=''* Any solution to this problem? On Jul 6, 10:46 pm, Kless [EMAIL PROTECTED] wrote: I'm using so: def Column0(*a, **k):     return Column(nullable=False, default='', *a, **k) groups_table = Table('foo',

[sqlalchemy] Re: nullable=False by default

2008-07-06 Thread Michael Bayer
On Jul 6, 2008, at 7:06 PM, Kless wrote: I think that there is a bug. autoincrement doesn't works with *default=''* Any solution to this problem? the docs for autoincrement need to be read closely. This flag only applies to Integer columns with the primary key flag set. I'm not