Would that use the rest API? - Cloudflare Developers

© 2026 Hedgehog Software, LLC

More

Communities Docs About Terms Privacy

Hello, I’m Allie!

H

Hello, I’m Allie!•5/8/24, 10:01 AM

It may be ok with WfP? IIRC you should be able to bind to an individual script

Natalie

NNatalie Would that use the rest API?

Hello, I’m Allie!

H

Hello, I’m Allie!•5/8/24, 10:04 AM

No, I believe it would be like a Durable Object, where you pass an ID in, and get a binding out

Hello, I’m Allie!

H

Hello, I’m Allie!•5/8/24, 10:05 AM

Though I'm not on the team, so that is just a guess on my part

Natalie

N

NatalieOP•5/8/24, 10:05 AM

Ah. Makes sense

Natalie

N

NatalieOP•5/8/24, 10:05 AM

Thanks

krofdrakula

K

krofdrakula•5/8/24, 1:38 PM

does anyone know if prepared statements can be bound with arrays? i'm trying to do a query like db.prepare('SELECT * FROM table WHERE status IN (?)').bind(['active','expired']).all()db.prepare('SELECT * FROM table WHERE status IN (?)').bind(['active','expired']).all(), would that work?

krofdrakula

Kkrofdrakula does anyone know if prepared statements can be bound with arrays? i'm trying to ...

roftt

R

roftt•5/8/24, 1:41 PM

https://discord.com/channels/595317990191398933/992060581832032316/1226795894280687636

Marcel Overdijk

M

Marcel Overdijk•5/8/24, 3:06 PM

The pricing docs for D1 mention:

Every query returns a meta object that contains a total count of the rows read (rows_read) and rows written (rows_written) by that query. For example, a query that performs a full table scan (for instance, SELECT * FROM users) from a table with 5000 rows would return a rows_read value of 5000:

"meta": {
  "duration": 0.20472300052642825,
  "size_after": 45137920,
  "rows_read": 5000,
  "rows_written": 0
}

These are also included in the D1 Cloudflare dashboard and the analytics API, allowing you to attribute read and write volumes to specific databases, time periods, or both.

Every query returns a meta object that contains a total count of the rows read (rows_read) and rows written (rows_written) by that query. For example, a query that performs a full table scan (for instance, SELECT * FROM users) from a table with 5000 rows would return a rows_read value of 5000:

"meta": {
  "duration": 0.20472300052642825,
  "size_after": 45137920,
  "rows_read": 5000,
  "rows_written": 0
}

These are also included in the D1 Cloudflare dashboard and the analytics API, allowing you to attribute read and write volumes to specific databases, time periods, or both.

But where can I see these rows_read statitiscs in the dashboard?

I'm trying to find out how count queries are calculated...

Imagine I have a select count(1) from customer where country_id = 'uk'select count(1) from customer where country_id = 'uk' what is the cost for such a query?
Is it equals to the number of rows in the customer table?

roftt

R

roftt•5/8/24, 3:24 PM

Try this in your worker:

const stmt = db.prepare('select count(1) from customer where country_id = "uk"').all();
console.log(stmt.meta.rows_read)

const stmt = db.prepare('select count(1) from customer where country_id = "uk"').all();
console.log(stmt.meta.rows_read)

Overall statistics for rows_read of the entire database is in Dashboard -> Your DB -> Metrics
And don't forget to use indexes, it reduces rows_read drastically

Marcel Overdijk

M

Marcel Overdijk•5/8/24, 5:27 PM

I'm wondering if I can check these query statistic per query executed from the console?

kian

K

kian•5/8/24, 5:31 PM

If you open DevTools, the

meta

meta

object will be in the HTTP response.

Marcel Overdijk

M

Marcel Overdijk•5/8/24, 5:38 PM

That was indeed useful.
So when a customercustomer table contains 900 records both queries
select * from customerselect * from customer and
select count(1) from customerselect count(1) from customer
will have "rows_read": 900,"rows_read": 900,

Marcel Overdijk

M

Marcel Overdijk•5/8/24, 5:39 PM

so countcount queries are quite expensive in D1

roftt

Rroftt should be VALUES (?1, ?2, ?3, ?4, ?5, ?6, ?7)

di_uthred

D

di_uthred•5/8/24, 6:37 PM

didn't make a difference

Marcel Overdijk

MMarcel Overdijk so `count` queries are quite expensive in D1

Isaac McFadyen

I

Isaac McFadyen•5/8/24, 7:41 PM

This is not really specific to D1 (but yeah that's accurate)

Isaac McFadyen

I

Isaac McFadyen•5/8/24, 7:41 PM

A lot of databases will read every row for "count" because they assume you want an exact count.

Isaac McFadyen

I

Isaac McFadyen•5/8/24, 7:42 PM

I believe there's some other databases (I think CockroachDB?) that will give you approximate counts without reading every row, but SQLite (and therefore D1) does not do this.

Unsmart

U

Unsmart•5/8/24, 10:11 PM

From how I am reading it the 1 per 1000 thing relates to indexes not documents. So you are always charged at minimum 1 read per document + something for indexes

Unsmart

U

Unsmart•5/8/24, 10:12 PM

Firestore also costs like 600x the price for reads so

Marcel Overdijk

M

Marcel Overdijk•5/8/24, 10:14 PM

I understand as it needs to actually read the rows.
Maybe this could be added to docs explicitly in the pricing section?

Unsmart

U

Unsmart•5/8/24, 10:18 PM

It is in the doc on the pricing page:

1. Rows read measure how many rows a query reads (scans), regardless of the size of each row. For example, if you have a table with 5000 rows and run a SELECT * FROM table as a full table scan, this would count as 5,000 rows read. A query that filters on an unindexed column may return fewer rows to your Worker, but is still required to read (scan) more rows to determine which subset to return.

Marcel Overdijk

M

Marcel Overdijk•5/8/24, 10:18 PM

Another thing I'm wondering now is the foolowing:
I'm implementing an api with a traditional pagination using offsetoffset,

limit

limit

(so no cursors).
Responses also include the totalCounttotalCount
Currently I'm executing 2 queries:
- get the actual records for the given page (e.g. with page size 1010 this will result in 10 rows being queried.
- the count query (so when having 1000 rows in the D1 database this will result in 1000 rows read)
together this will result in 1010 rows being read
I could in fact just query all rows (1000!! reads) and then do the filtering (pagination) in the code....

Unsmart

UUnsmart It is in the doc on the pricing page: > 1. Rows read measure how many rows a que...

Marcel Overdijk

M

Marcel Overdijk•5/8/24, 10:19 PM

I mean explicitly stating that a count query will also perform these reads (so count resulting in value 1000, will mean 1000 rows read)

Marcel Overdijk

M

Marcel Overdijk•5/8/24, 10:21 PM

Above does not seem effective but will cost 10 reads less... I'm not concerned about those 10 more reads btw.
But maybe executing 1 query instead of 2 might even perform better....

Marcel Overdijk

M

Marcel Overdijk•5/8/24, 10:23 PM

The tables I'm quering this way will not contain more than 1000 rows on average.

Marcel Overdijk

MMarcel Overdijk Another thing I'm wondering now is the foolowing: I'm implementing an api with a...

Isaac McFadyen

I

Isaac McFadyen•5/8/24, 10:29 PM

I'd strongly recommend against the "query all the rows" approach.

Isaac McFadyen

I

Isaac McFadyen•5/8/24, 10:30 PM

Workers have memory limits so if you filter in the Worker you'll still run into issues where if the rows are very large and a script is being executed by 2 people then you might hit those limits

Isaac McFadyen

I

Isaac McFadyen•5/8/24, 10:30 PM

Plus you'll be billed more for processing time in the Worker itself (which is likely more than the extra 10 reads from D1)

Marcel Overdijk

M

Marcel Overdijk•5/8/24, 10:49 PM

Yes I’m also against it.

Marcel Overdijk

M

Marcel Overdijk•5/8/24, 10:51 PM

But I might instead cache the result of the count query, as it is quite static data.

Marcel Overdijk

M

Marcel Overdijk•5/8/24, 10:56 PM

Yes that could be an option.
But I also have other filter arguments besides offset limit…
Like country, category etc. In the api 0, 1 or more of the filters can be applied.

Marcel Overdijk

M

Marcel Overdijk•5/8/24, 11:02 PM

No 0, 1 or more column based filters + limit / offset.
Where normally the limit is 10 so 10 rows are returned. But also the total count based on the filters is needed. (To show navigation buttons)

Marcel Overdijk

M

Marcel Overdijk•5/8/24, 11:03 PM

So result is 10 rows (based on limit param) but count could be 300, 400 or like 1000

wiln

W

wiln•5/8/24, 11:26 PM

Hello, I am new to D1, I want to ask if it is possible to read and write to the database using the python code on my computers? It makes me feel like you can only do that using javascript and workers

Isaac McFadyen

I

Isaac McFadyen•5/9/24, 3:30 AM

TIL, that's cool

Unsmart

U

Unsmart•5/9/24, 3:48 AM

neat, never made a table without an index personally so would always work well

matt

M

matt•5/9/24, 7:43 AM

im a little confused by some of the language in the d1 material I've been reading -- are read replicas available now?

matt

Mmatt im a little confused by some of the language in the d1 material I've been readin...

Hello, I’m Allie!

H

Hello, I’m Allie!•5/9/24, 7:44 AM

They are not

matt

M

matt•5/9/24, 7:46 AM

ah ok thanks for the update. the blog post from april makes it sounds like they are already running. did CF provide any timelines for when they might be available? really like the look of the session API and can't wait to try it out

matt

Mmatt ah ok thanks for the update. the blog post from april makes it sounds like they ...

Hello, I’m Allie!

H

Hello, I’m Allie!•5/9/24, 7:46 AM

:soontm:

Hello, I’m Allie!

H

Hello, I’m Allie!•5/9/24, 7:46 AM

Best answer we can give you atm

Every query returns a meta object that contains a total count of the rows read (rows_read) and rows written (rows_written) by that query. For example, a query that performs a full table scan (for instance, SELECT * FROM users) from a table with 5000 rows would return a rows_read value of 5000:

"meta": {
  "duration": 0.20472300052642825,
  "size_after": 45137920,
  "rows_read": 5000,
  "rows_written": 0
}

These are also included in the D1 Cloudflare dashboard and the analytics API, allowing you to attribute read and write volumes to specific databases, time periods, or both.

Every query returns a meta object that contains a total count of the rows read (rows_read) and rows written (rows_written) by that query. For example, a query that performs a full table scan (for instance, SELECT * FROM users) from a table with 5000 rows would return a rows_read value of 5000:

"meta": {
  "duration": 0.20472300052642825,
  "size_after": 45137920,
  "rows_read": 5000,
  "rows_written": 0
}

These are also included in the D1 Cloudflare dashboard and the analytics API, allowing you to attribute read and write volumes to specific databases, time periods, or both.