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 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 <[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 > >>> fields with a string empty. > > >> im not sure offhand what an empty string would produce since I'd have > >> to check what we're doing to detect "no value present". But I would > >> hope that if the string value went through, it would raise an error > >> on > >> the DB side (so this impies you might be using SQLite). --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
