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 being autoincremented, after of the Column subclass.
>
> On Jul 7, 3:45 am, Michael Bayer <[EMAIL PROTECTED]> wrote:
>
> > 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  
> > sure what interaction it would be expected to have with "default" in  
> > any case (default is all you need if you have a custom default  
> > generation function).
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sqlalchemy?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to