U
M
HM
created_at column of a users tableSELECT * FROM users WHERE created_at = ?1 - that will use the index to look up the rows in the users table. This means there is a read on the index, and then a (MUCH SMALLER) read on the users table as you no longer have to do a full scan for the row(s) matching your created_at filter.users table, if your query only matches one row)HHMM
M
SELECT * 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_written and rows_read and I am kinda surprised to find written rows in a SELECT queryTMU
MH
J
KJJJJT
rows_written and rows_read in every result, could we imagine some total_rows_written and total_rows_read in a "status" request?MMMTJC
back from pushing the limits over 500MB? 
C
.batch() it gets auto transactionCEXPLAIN statement. The column name is messed up? 
DD
created_atcreated_atusersusersusersusersSELECT * 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 LIKErows_writtenrows_writtenrows_readrows_readtotal_rows_writtentotal_rows_read.batch()EXPLAIN