On Wed, Sep 8, 2010 at 5:01 PM, Andrew Wood <[email protected]> wrote:
> Because I'm writing glue code between the SQLite API and a higher level > library which provides a standard API across several DBMSs. > > In other DBMSs even if a field contains null you can still ask the API > what type it 'should' have been if something *had* been put in it. > Without this ability, I cant make SQLite work with the library. > > I don't understand the reasoning for designing SQLite weakly typed like > this, it just seems bizarre. > SQLite is not "weakly" typed. It is flexibly typed. And all those other SQL database engines are "rigidly" typed. Flexible typing in SQLite is a Good Thing, for the same reason that it is a good thing in AWK, TCL, Perl, Python, Ruby, Lua, Javascript, etc. -- D. Richard Hipp [email protected] _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
