On 17 Sep 2013, at 12:32am, James K. Lowden <[email protected]> wrote:
> I suggest that when the observed behavior is known to be at variance > with what is specified in the SQL standard, it should be viewed as a > defect and as a candidate for revision. If it also fails on > theoretical grounds -- as when atomicity is promised but not supplied > -- it should be added to the list of known bugs until it's rectified. Presumably it should be added to <http://sqlite.org/omitted.html> or something like it. Actually, while I feel that this is a problem with respect to CURRENT_TIME, etc., since Kees pointed out that this is defined in the SQL standard, I have no real problem with current behaviour when 'now' is used with the datetime functions. Unless someone finds that /that/ is in the standard too. Wonder whether it can be fixed in SQLite4. Simon. _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
