rows_written and rows_read in the metadata for every query. Documentation landing soon. e.g.
rows_writtenrows_read➜ wrangler d1 execute db-enam --command "INSERT INTO users(email_address,created_at,deleted,settings) VALUES ('me@example.com,', 1687904983, null, '{}')" --json
[
{
"results": [],
"success": true,
"meta": {
"duration": 0.17432300001382828,
"size_after": 45137920,
"rows_read": 0,
"rows_written": 2 // Two rows: one to the table, and one to the index as there's an index on created_at for this table
}
}
]
M
K
UM
IU
HUMHM
created_atusersSELECT * FROM users WHERE created_at = ?1 - that will use the index to look up the rows in the usersuserscreated_atusers
MSELECT * FROM table LIMIT N - yes. But if you have a filter like a WHERE or HAVING clause, then you have to scan more rows to match the filter, since your table isn't necessarily ordered.U
MORDER in that query. But it has to scan the table somehow - usually a binary search. It's going to keep searching (scanning) until it has matched all possible records, or hit the LIMITUUMLIMIT 10M
MORDER BY <some_date_column> queries. I probably need to add this to the docs.M
U
H
CSQL LIKE? M
M
T
rows_writtenrows_read
MH
JKJJJJT
rows_writtenrows_readtotal_rows_written and total_rows_read in a "status" request?MMMTWhile in the Open Alpha period, there is a possibility of breaking changes. The Alpha is meant for testing purposes and using it for production traffic is not recommended.SELECT * FROM users WHERE created_at = ?1SELECT * FROM table LIMIT NWHEREHAVING➜ wrangler d1 execute db-wnam --command "SELECT * FROM [Order] WHERE ShipRegion LIKE '%Western%' LIMIT 10" --json | jq '.[].meta.rows_read'
18 <-- we had to scan 18 rows to find 10 that matched our filterORDERLIMITLIMIT 10ORDER BY <some_date_column>SQL LIKEtotal_rows_writtentotal_rows_read