On 11/4/05, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > > On 11/4/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Why am I not getting a TIMESTAMP type instead of datetime. Preferably > > I would like a timestamp with timezone. > > As somebody who doesn't use SQLite, I must ask: What advantage does > timestamp offer over datetime? I can't find any mention of it on > http://www.sqlite.org/datatype3.html . > > > Also choices are not generating a check statement like: > > status VARCHAR(8) CHECK (status in ('active', 'inactive')), > > The choices are implemented at the Python level, not at the database > level. Feel free to add the CHECK to your SQL manually. > > django-admin.py sqlall myapp > myapp.sql > vim myapp.sql # add the CHECK > cat myapp.sql | sqlite # pipe the SQL into SQLite, however that's done > > Adrian > > -- > Adrian Holovaty > holovaty.com | djangoproject.com | chicagocrime.org >
According to this page: http://www.sqlite.org/lang_createtable.html TIMESTAMP is not a type but a default value for a column as in DEFAULT=TIMESTAMP. And from this page: http://www.sqlite.org/different.html we learn that "SQLite... allows the user to store any value of any datatype into any column regardless of the declared type of that column." Which basicly means declaring a datatype does nothing for SQLite (except for an INTEGER PRIMARY KEY or a few other rare exceptions). I don't know, does django compensate for this? Making it work like other DBs? Or should fairwinds be altering the tables for his needs? Either way, it certainly makes the case for validating data before writing it to your db. -- ---- Waylan Limberg [EMAIL PROTECTED]
