Howdy!
The SQLite3 Tcl interface has a "nullvalue" command, which determines how NULLs
are represented as Tcl values. If you do a query on a NULL value, you get the
"nullvalue" value. ("nullvalue" defaults to the empty string.)
However, if a NULL value is passed to a custom SQL function, defined using the
Tcl [$db function] command, the function body (a Tcl proc) appears to get the
empty string instead of the desired "nullvalue" for the given value. This
seems like a bug to me. Am I wrong?
I'm using SQLite3 3.7.7.1; the function is called from a trigger (if that
matters).
Will
--
Will Duquette -- william.h.duque...@jpl.nasa.gov
Athena Development Lead -- Jet Propulsion Laboratory
"It's amazing what you can do with the right tools."
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
