Yes, we use it, why do you ask?
Yes, we use it, why do you ask?

wrangler d1 insights command: https://developers.cloudflare.com/d1/observability/metrics-analytics/#query-insights
--timePeriod flag like in the last example on that page.--timePeriod=7d etc.{
"name": "my-database"
}
DELETE statement from a sql file, the metric returned in the terminal (the same number is in the web dashboard) for rows read was astronomically bigger than it should be:prods db has close to 12K rows (yes 12_000, not 12M).tid is indexed. The statement was correctly applied and it took only a couple of seconds..scanstats on:
near "��P": syntax error at offset 0: SQLITE_ERROR [code: 7500], and yes I followed the steps in the guide and yes I tried to remove the line and checked for invisible charswrangler d1 insights--timePeriod--timePeriod=7d{
"name": "my-database"
}DELETEprodstid.scanstats onnear "��P": syntax error at offset 0: SQLITE_ERROR [code: 7500]npx wrangler d1 execute prods --file $rm_rows_sql --remote
#returns
rows read: 70344030 (web dash display 70.72M)sqlite> .read del_not_shared.sql
QUERY PLAN (cycles=113272102 [100%])
`--SEARCH products USING INTEGER PRIMARY KEY (rowid=?) (cycles=26065003 [23%] loops=1 rows=1272)-- Create a simple table
DROP TABLE IF EXISTS test_table;
CREATE TABLE IF NOT EXISTS test_table (
id INTEGER PRIMARY KEY AUTOINCREMENT,
name TEXT,
updated_at DATETIME DEFAULT CURRENT_TIMESTAMP
);
-- Drop any existing trigger
DROP TRIGGER IF EXISTS test_trigger;
-- Create a simple trigger
CREATE TRIGGER test_trigger
AFTER UPDATE ON test_table
FOR EACH ROW
BEGIN
UPDATE test_table
SET updated_at = CURRENT_TIMESTAMP
WHERE id = OLD.id;
END;DELETE FROM products WHERE tid IN (5, 22, 34, 38, 41, 50, 57, 64, 90, 98,..)