, @rozenmd, can I expect it to work at some point or not? Just to design the schema and Workers accordingly.
MMM
fts5 instead of FTS5? looks like a bug
I
M
unixepoch is supported. Does that create table statement work outside of D1? Usually you can’t have functions like that.M
MM
MMMM
L{
"message": "Error while checking rows: Error: D1_ERROR\n at D1Database._send (worker.js:149:13)\n at async D1PreparedStatement.all (worker.js:215:7)\n at async Object.fetch (worker.js:11:18)"
}M
M
--experimental-backend or the original alpha backend?MMImportantly, when we enable global read replication, you won’t have to pay extra for it, nor will replication multiply your storage consumption
M
I
SELECT query, will those be split to a separate replica?IMMI
) where the consumers for queues would run to locate the db closer to there (especially with the replicas on the horizon as the users would hit only the read side)IIMMWAL provides more concurrency as readers do not block writers and a writer does not block readers. Reading and writing can proceed concurrently.
I
.sql file if you really want to (up to a point)I1.1.1.1 fetch and it's a queue consumer, so who knows. Will report back if it becomes a pattern fts5FTS5unixepoch{
"message": "Error while checking rows: Error: D1_ERROR\n at D1Database._send (worker.js:149:13)\n at async D1PreparedStatement.all (worker.js:215:7)\n at async Object.fetch (worker.js:11:18)"
}--experimental-backendSELECT.sql1.1.1.1