Jim Dodgen wrote: > On Sun, Sep 23, 2012 at 3:37 AM, Baruch Burstein <bmburst...@gmail.com> wrote: >> I am curious about the usefulness of sqlite's "unique" type handling, and >> so would like to know if anyone has ever actually found any practical use >> for it/used it in some project? I am referring to the typeless handling, >> e.g. storing strings in integer columns etc., not to the non-truncating >> system e.g. storing any size number or any length string (which is >> obviously very useful in many cases). >> Has anyone ever actually taken advantage of this feature? In what case? > > 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. (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
