RTREE only understands floating-point numbers (or integers if you use
"rtree_i32" instead of "rtree"). It does not do NULLs or strings or
blobs. If you give it one of these other values, it will try to convert
that value into a floating-point number as best it can.
The best it can do with a NULL
So, I was looking at some triggers to update an RTREE virtual table that
someone
else wrote. I noticed that the trigger didn't handle NULLs. I was curious,
and
decided to see what happened if you tried to insert NULL values into an RTREE.
Actually, I rather expected it to throw an error. I
2 matches
Mail list logo