mirror
/
tile38
mirror of https://github.com/tidwall/tile38.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
tile38/tests/json_test.go

42 lines
2.1 KiB
Go
Raw Normal View History

added JSET, JGET, JDEL commands JSET key id path value [RAW] JGET key id path [RAW] JDEL key id path Allows for working with JSON strings, for example: JSET user 901 name Tom JGET user 901 > '{"name":"Tom"}' JSET user 901 name.first Tom JSET user 901 name.last Anderson > '{"name":{"first":"Tom","last":"Anderson"}' JDEL user 901 name.last > '{"name":{"first":"Tom"}' All commands use the GJSON path syntax, for more information: Setting JSON: https://github.com/tidwall/sjson Getting JSON: https://github.com/tidwall/gjson
2016-12-12 20:33:28 +03:00
package tests
import "testing"
func subTestJSON(t *testing.T, mc *mockServer) {
runStep(t, mc, "basic", json_JSET_basic_test)
runStep(t, mc, "geojson", json_JSET_geojson_test)
}
func json_JSET_basic_test(mc *mockServer) error {
return mc.DoBatch([][]interface{}{
{"JSET", "mykey", "myid1", "hello", "world"}, {"OK"},
{"JGET", "mykey", "myid1"}, {`{"hello":"world"}`},
{"JSET", "mykey", "myid1", "hello", "planet"}, {"OK"},
{"JGET", "mykey", "myid1"}, {`{"hello":"planet"}`},
{"JSET", "mykey", "myid1", "user.name.last", "tom"}, {"OK"},
{"JSET", "mykey", "myid1", "user.name.first", "andrew"}, {"OK"},
{"JGET", "mykey", "myid1"}, {`{"user":{"name":{"first":"andrew","last":"tom"}},"hello":"planet"}`},
{"JDEL", "mykey", "myid1", "user.name.last"}, {1},
{"JGET", "mykey", "myid1"}, {`{"user":{"name":{"first":"andrew"}},"hello":"planet"}`},
{"JDEL", "mykey", "myid1", "user.name.last"}, {0},
{"JGET", "mykey", "myid1"}, {`{"user":{"name":{"first":"andrew"}},"hello":"planet"}`},
{"JDEL", "mykey2", "myid1", "user.name.last"}, {0},
})
}
Faster point in polygon / GeoJSON updates The big change is that the GeoJSON package has been completely rewritten to fix a few of geometry calculation bugs, increase performance, and to better follow the GeoJSON spec RFC 7946. GeoJSON updates - A LineString now requires at least two points. - All json members, even foreign, now persist with the object. - The bbox member persists too but is no longer used for geometry calculations. This is change in behavior. Previously Tile38 would treat the bbox as the object's physical rectangle. - Corrections to geometry intersects and within calculations. Faster spatial queries - The performance of Point-in-polygon and object intersect operations are greatly improved for complex polygons and line strings. It went from O(n) to roughly O(log n). - The same for all collection types with many children, including FeatureCollection, GeometryCollection, MultiPoint, MultiLineString, and MultiPolygon. Codebase changes - The pkg directory has been renamed to internal - The GeoJSON internal package has been moved to a seperate repo at https://github.com/tidwall/geojson. It's now vendored. Please look out for higher memory usage for datasets using complex shapes. A complex shape is one that has 64 or more points. For these shapes it's expected that there will be increase of least 54 bytes per point.
2018-10-11 00:25:40 +03:00
added JSET, JGET, JDEL commands JSET key id path value [RAW] JGET key id path [RAW] JDEL key id path Allows for working with JSON strings, for example: JSET user 901 name Tom JGET user 901 > '{"name":"Tom"}' JSET user 901 name.first Tom JSET user 901 name.last Anderson > '{"name":{"first":"Tom","last":"Anderson"}' JDEL user 901 name.last > '{"name":{"first":"Tom"}' All commands use the GJSON path syntax, for more information: Setting JSON: https://github.com/tidwall/sjson Getting JSON: https://github.com/tidwall/gjson
2016-12-12 20:33:28 +03:00
func json_JSET_geojson_test(mc *mockServer) error {
return mc.DoBatch([][]interface{}{
{"SET", "mykey", "myid1", "POINT", 33, -115}, {"OK"},
{"JGET", "mykey", "myid1"}, {`{"type":"Point","coordinates":[-115,33]}`},
{"JSET", "mykey", "myid1", "coordinates.1", 44}, {"OK"},
{"JGET", "mykey", "myid1"}, {`{"type":"Point","coordinates":[-115,44]}`},
{"SET", "mykey", "myid1", "OBJECT", `{"type":"Feature","geometry":{"type":"Point","coordinates":[-115,44]}}`}, {"OK"},
{"JGET", "mykey", "myid1"}, {`{"type":"Feature","geometry":{"type":"Point","coordinates":[-115,44]}}`},
{"JGET", "mykey", "myid1", "geometry.type"}, {"Point"},
{"JSET", "mykey", "myid1", "properties.tags.-1", "southwest"}, {"OK"},
{"JSET", "mykey", "myid1", "properties.tags.-1", "united states"}, {"OK"},
{"JSET", "mykey", "myid1", "properties.tags.-1", "hot"}, {"OK"},
{"JGET", "mykey", "myid1"}, {`{"type":"Feature","geometry":{"type":"Point","coordinates":[-115,44]},"properties":{"tags":["southwest","united states","hot"]}}`},
Faster point in polygon / GeoJSON updates The big change is that the GeoJSON package has been completely rewritten to fix a few of geometry calculation bugs, increase performance, and to better follow the GeoJSON spec RFC 7946. GeoJSON updates - A LineString now requires at least two points. - All json members, even foreign, now persist with the object. - The bbox member persists too but is no longer used for geometry calculations. This is change in behavior. Previously Tile38 would treat the bbox as the object's physical rectangle. - Corrections to geometry intersects and within calculations. Faster spatial queries - The performance of Point-in-polygon and object intersect operations are greatly improved for complex polygons and line strings. It went from O(n) to roughly O(log n). - The same for all collection types with many children, including FeatureCollection, GeometryCollection, MultiPoint, MultiLineString, and MultiPolygon. Codebase changes - The pkg directory has been renamed to internal - The GeoJSON internal package has been moved to a seperate repo at https://github.com/tidwall/geojson. It's now vendored. Please look out for higher memory usage for datasets using complex shapes. A complex shape is one that has 64 or more points. For these shapes it's expected that there will be increase of least 54 bytes per point.
2018-10-11 00:25:40 +03:00
{"JDEL", "mykey", "myid1", "type"}, {"ERR missing type"},
added JSET, JGET, JDEL commands JSET key id path value [RAW] JGET key id path [RAW] JDEL key id path Allows for working with JSON strings, for example: JSET user 901 name Tom JGET user 901 > '{"name":"Tom"}' JSET user 901 name.first Tom JSET user 901 name.last Anderson > '{"name":{"first":"Tom","last":"Anderson"}' JDEL user 901 name.last > '{"name":{"first":"Tom"}' All commands use the GJSON path syntax, for more information: Setting JSON: https://github.com/tidwall/sjson Getting JSON: https://github.com/tidwall/gjson
2016-12-12 20:33:28 +03:00
})
}