Hi there. There is no advantage/disadvantage to the expression, this is mainly a portability issue me since I generally use the same SQL for web based applications with Postgres and with SQLite for embedded apps.
Waylan is right, SQLite has few types but and you can put pretty much anything in. Its sort of an interesting database. TIMESTAMP is what I anticipated based on the model. I have used SQLObject in the past to generate SQL for SQLite with TIMESTAMP so perhaps it was out of this experience that I was suprised it was not generated from Django. How can time zone be included from my model? Also. I was just reading about install and found something about including .sql files in a sql folder in the project directory. I guess the alter table statement could be included here. I am assuming the sql from the install gets loaded after the tables are created. On check statement is there any thought in including an EnumeratedField type in models that could take the elements from the choice tuple and create the check statement. I know MySQL uses a non stadard enumerated type but the CHECK statement is standard SQL. I have validation code I have written that I am planning on reusing from my web apps. I was looking at seeing what could be done with Django's validators once my models are all working the way I want. I am using Django to write a cross platform Desktop app so am not certain that I will be generating any views since I am writing GUI code. I believe from what I have been reading that I would just have to import the manipulators to implement validation (whether or not I am writing a view). I am hoping to pass the validator messages to dialogs boxes in my GUI this way. Regards David
