M
G
J
Are there any plans to add spacial data support to D1 for geo-lookups? Maybe adding an extension like Spatialite (ideally), or enabling R*Tree support?
M
LJ
J
.dump in execute?
CJJ
execute --command select * from ... for each table and writing import scripts. So I'm not blocked per se ... just expected to have some way to dump the db 
CM
K.dump is more or less doing the same thing as the exporters. It's purely a SQLite3 shell command, rather than being available in their C API (which embedders like Workers use) so it would need the functionality written up rather than being something they can enable or use from SQLite.MKK
JKThe double-quoted string misfeature is now disabled by default for CLI buildsnevermind, thankfully that's gone in 3.41.0
KK
VK
KRKK
user: token then you might read user and there's nothing, so you now have a cached 404.Ktoken: user, then there is no reason for you to read it before you've generated the token so it's more resistant to having cached 404's.K
F
U
SSMSS
WG
FGF
FGG
C
CC
d1api.first`SELECT * FROM users WHERE id = ${id}`
PC
.dump.dumpexecute --command select * from ...user: tokenusertoken: userd1api.first`SELECT * FROM users WHERE id = ${id}`