Avoiding NULLs is always good I think. But since SQLite itself works
fine with them and LiveCode doesn't, this feels like a bug to me.
Should I enter it at the QCC?
Pete Haworth
On Nov 15, 2010, at 3:06 PM, Bob Sneidar wrote:
Ah hah! Nice catch. I thought Rev was supposed to interpret NULL as
empty string, but with the concatenation, I suppose the NULL's would
be embedded in the returned pseudo column (probably not the right
word for it). That is a nice little gotcha there for anyone running
this kind of query. Moral to story: avoid NULL values in LiveCode
SQL databases?
Bob
On Nov 15, 2010, at 2:58 PM, Peter Haworth wrote:
Thanks Bob. I think the problem may have something to do with NULL
values in some of the columns coming back from the SELECT. When I
fixed them, the SELECT worked fine in LiveCode. The Firefox plugin
was one of the utilities I used to check this out and it returned
all the data correctly, even when there were NULLs in the columns.
Pete Haworth
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
