On Sun, Sep 23, 2012 at 10:25 AM, Yuriy Kaminskiy <yum...@gmail.com> wrote: > Jim Dodgen wrote: >> I program mostly on Perl on Linux and it is a beautiful fit. Example >> is I can have a date field with a POSIX time value (or offset) in it >> or another date related value like "unknown" > > Very bad example. Standard SQL NULL is much better fit for "unknown". > Besides, perl at least have "use strict;" and "use warnings;", sqlite does > not.
On "unknown" was not the best example. but other values could be "missing from input", "preferred not to give" or anything else that fits the problem with just the null I only get two states. "good, and "bad", sometimes things for me are more complex > > (Not that I expect anything to change here; backward compatibility, > requirement > to keep it "lite", etc; like it or not, we have live with current lax typing > system) > -- > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > A: Top-posting. > Q: What is the most annoying thing on usenet and in e-mail? > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users -- Jim Dodgen Watch our travels at: WinoTrips.com _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
