On Mar 10, 2010, at 7:36 AM, Israel Lins Albuquerque wrote: > In this new version: > > > at file date.c line 1095 are changed? Why? > > previous version > STR_FUNCTION(current_date, 0, "%Y-%m-%d", 0, currentTimeFunc), > STR_FUNCTION(current_timestamp, 0, "%Y-%m-%d %H:%M:%S", 0, > currentTimeFunc), > > new version > STR_FUNCTION(current_timestamp, 0, "%Y-%m-%d", 0, currentTimeFunc), > STR_FUNCTION(current_date, 0, "%Y-%m-%d %H:%M:%S", 0, > currentTimeFunc), > > I fink this is a problem because: > SELECT CURRENT_DATE will return 2010-03-10 09:34:55 > SELECT CURRENT_TIMESTAMP will return 2010-03-10 > > Are this correct?
I think you have it backwards. What you have labeled as "previous version" above is what the current code looks like and your "current version" is what it used to look like. See http://www.sqlite.org/src/ci/eb98265b59 for a diff of the change. This was a bug fix. The code in question only comes into play when you compile with SQLITE_OMIT_DATETIME_FUNCS and so it doesn't matter for most people. We didn't discover the problem until recently when we were adding some tests that make use of SQLITE_OMIT_DATETIME_FUNCS. > > > Regards , > > Israel Lins Albuquerque > Developer > Polibrás Brasil Software Ltda. > > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users D. Richard Hipp d...@hwaci.com _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
