On 9/1/08, jonwood <[EMAIL PROTECTED]> wrote: > > > P Kishor-3 wrote: > > > > Don't think it is possible. As you noted, the docs say very clearly > > (http://www.sqlite.org/lang_createtable.html) -- " The DEFAULT > > constraint specifies a default value to use when doing an INSERT. .. > > default value may also be one of the special case-independant keywords > > CURRENT_TIME, CURRENT_DATE or CURRENT_TIMESTAMP. ... If the value is > > CURRENT_TIME, CURRENT_DATE or CURRENT_TIMESTAMP, then the current UTC > > date and/or time is inserted into the columns. " > > > > > Thanks for your input. This is really a shame, and quite surprising, that it > works this way with no means to modify the behavior. There are all sorts of > flags to modify how the source code works, but I could find nothing related > to this. Based on my previous searches, I am not the only one who thinks it > should work this way. It should at least be an option.
well, maybe. How data are stored is/should_be irrelevant to the end user. In fact, the best way to store dates might well be just numbers (search the archives for discussions on how to best store dates/times). The key is in retrieving and displaying (or doing whatever one wants to do with them) the data. You have all the options in the world to use the datetime functions for that, or, even more so in your application. All you have to do is to remember how your data were inserted in the first place. > > Thanks. > > -- > View this message in context: > http://www.nabble.com/Default-Column-Value-to-Local-Time-tp19263208p19263371.html > > Sent from the SQLite mailing list archive at Nabble.com. > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
