tile38/internal
tidwall aa1caa6131 Use zero for undefined fields in where expressions
This commit fixes an issue where expressions were
silently failing when encountering undefined fields.
Instead they should be treating the undefined field like
the number zero. This is required to stay compatible with
how Tile38 handles zeros.
https://tile38.com/commands/intersects/#fields

Fixes #754
2024-11-05 14:03:23 -07:00
..
bing Code cleanup 2019-10-30 10:17:59 -07:00
buffer Fixed invalid BOUNDS result 2022-11-21 04:47:56 -07:00
clip Code cleanup 2021-07-08 06:46:08 -07:00
collection Allow for queries GeoJSON properties 2022-10-20 14:26:34 -07:00
deadline Cleanup code for Go 1.19 2022-09-12 17:06:27 -07:00
endpoint chore: fix some typos in comments 2024-04-11 11:16:44 +08:00
field Merge pull request #731 from oftenoccur/master 2024-06-03 19:36:24 -07:00
glob Cleanup code for Go 1.19 2022-09-12 17:06:27 -07:00
hservice Faster point in polygon / GeoJSON updates 2018-10-13 04:30:48 -07:00
log Thread safe log and support for concurrent tile38 instances 2022-09-26 10:02:02 -07:00
object Update btree and minor optz 2022-09-21 18:29:01 -07:00
server Use zero for undefined fields in where expressions 2024-11-05 14:03:23 -07:00
sstring Field overhaul 2022-09-19 17:47:38 -07:00