Did they fix parsing a JSON boolean between XE5 and the current version? In XE5, if I put true (without quotes), I get the empty string. If I put "true" in quotes, I get true. In Berlin, if I put true without the quotes, I get true.
Booleans in JavaScript are weird. Well, actually everything related to variable types is. They say it's supposed to work by magic, but it just doesn't. Anyway, back to booleans: In one ETL tool I use, we need to use a "Mapper" step to turn booleans into strings "True" or "False" just before the final DB-table-writer step. Forget that -- or do it earlier in the chain -- and they're turned (back) into "yes" or "no", which the DB driver will not recognise as booleans.
So in XE5, a boolean wasn't really supported. You had to put quotes around it. In Berlin (and maybe earlier), this was fixed so that the unquoted true or false came over as true or false.
Booleans in JavaScript are weird. Well, actually everything related to variable types is. They say it's supposed to work by magic, but it just doesn't. Anyway, back to booleans: In one ETL tool I use, we need to use a "Mapper" step to turn booleans into strings "True" or "False" just before the final DB-table-writer step. Forget that -- or do it earlier in the chain -- and they're turned (back) into "yes" or "no", which the DB driver will not recognise as booleans.
ReplyDeleteNicholas Ring It's literally the simplest and best written spec ever. You can read.
ReplyDeleteSo in XE5, a boolean wasn't really supported. You had to put quotes around it. In Berlin (and maybe earlier), this was fixed so that the unquoted true or false came over as true or false.
ReplyDelete