> Taking into consideration a declared close relativity between SQLite and > TCL, I would to suggest an improvement in boolean-type fields treatment. > In my opinion, field of that type should be treated equally, when it does > contain a values: "f", "false", 0, "no" - and, respectively: "t", "true", > 1, "yes".
My understanding is that SQLite provides an extension mechanism for exactly this sort of thing, does it not? Besides which, where do you stop? "Present", "Absent", "on", "off", "here", "there", ".t.", ".f.", "da", "nein"? What about non-zero values generally representing true? Brad _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users