I see scale to zero is offered with D1. Does that mean the database spins down / goes to sleep after

I see scale to zero is offered with D1. Does that mean the database spins down / goes to sleep after a period of inactivity? If so, what is the latency to wake it from inactive?

EEnvy I recently changed some of my write queries that were doing INSERT OR REPLACE to...

Isaac McFadyen•3/18/24, 5:21 PM

Indexes count for a row written - could that be the reason?

Isaac McFadyen•3/18/24, 5:21 PM

If you have 4 indexes it will write 5 times (row + 4 indexes)

Kkelbs I see scale to zero is offered with D1. Does that mean the database spins down /...

Isaac McFadyen•3/18/24, 5:22 PM

D1 is built on SQLite. So it's actually not running at all when it's not being used. SQLite also makes spin-ups near-instant though.

kelbsOP•3/18/24, 5:23 PM

Turso claims 500ms latency to start up an inactive sqlite db on their system. Maybe there are differences between that and D1 though e.g. they're using libSQL

kelbsOP•3/18/24, 5:24 PM

https://docs.turso.tech/features/scale-to-zero

IIsaac McFadyen If you have 4 indexes it will write 5 times (row + 4 indexes)

Envy•3/18/24, 5:25 PM

Yeah that might be it

Kkelbs Turso claims 500ms latency to start up an inactive sqlite db on their system. Ma...

Isaac McFadyen•3/18/24, 5:27 PM

So one of the differences between Turso and D1 is that Turso actually runs a server for serving SQLite queries using libSQL as you said. D1 directly accesses SQLite on the node where your data is stored so the latency is basically the amount of time to open the DB and actually run the query (plus the time to get to the node where your DB is of course).

Isaac McFadyen•3/18/24, 5:28 PM

I believe Turso actually runs on Fly.io Machines so that would explain the spin-up latency.

kelbsOP•3/18/24, 5:29 PM

Gotcha, thank you. Would like to compare query latencies between the two if I can get everything hooked up

IIsaac McFadyen Indexes count for a row written - could that be the reason?

Envy•3/18/24, 5:30 PM

Yeah it was the indexes. I forgot I added a bunch of indexes that I really don't need on that table based on the extra cost of all the writes

Mmare arcis Is D1 effectively limited to 32000 insertions per worker invocation? 1000 subreq...

Max (@rozenmd)•3/19/24, 6:47 AM

what's your use case?

NNicolas Hi all, So I am trying to see how I can use D1 in a multi-tenant fashion. Su...

digendee•3/19/24, 9:23 AM

Hi Nick, did you get a reply about this, or figure anything out about it on your own?

Billy•3/19/24, 12:21 PM

I'm trying to get my local d1 database from one local project to another local project, i.e., from one dir to another dir without re-running the

wrangler d1 execute --local --file=.sql

wrangler d1 execute --local --file=.sql

approach. I thought I could just move the

.wrangler/state/v3/d1

.wrangler/state/v3/d1

dir over to another dir and spin things up but that did not work. Is there some other approach I could use?

My problem is that I use a separate worker to load portions of the database and I was hoping to avoid moving that worker and its config over to another dir temporarily to get the database fully loaded.

Thanks!

BBilly I'm trying to get my local d1 database from one local project to another local p...

Hello, I’m Allie!•3/19/24, 12:22 PM

Just to confirm, do both projects have the same

database_id

database_id

database_name

database_name

BBilly I'm trying to get my local d1 database from one local project to another local p...

Max (@rozenmd)•3/19/24, 12:23 PM

if you use --persist-to I think both Workers can talk to the same local db

HHello, I’m Allie!Just to confirm, do both projects have the same `database_id` & `database_name`?

Billy•3/19/24, 12:27 PM

yes they do

MMax (@rozenmd)if you use --persist-to I think both Workers can talk to the same local db

Billy•3/19/24, 12:27 PM

that's a good idea, I'll give that shot. Thanks

Billy•3/19/24, 12:29 PM

just to confirm, there's no way to dump the local db into a .sql file, correct?

BBilly just to confirm, there's no way to dump the local db into a .sql file, correct?

Max (@rozenmd)•3/19/24, 12:29 PM

locally if you have the sqlite3 binary you can open the

.sqlite

.sqlite

file and run

.dump

.dump

BBilly just to confirm, there's no way to dump the local db into a .sql file, correct?

Max (@rozenmd)•3/19/24, 12:30 PM

https://developers.cloudflare.com/d1/build-with-d1/import-data/#convert-sqlite-database-files

MMax (@rozenmd)locally if you have the sqlite3 binary you can open the `.sqlite` file and run `...

Billy•3/19/24, 12:51 PM

Right, I need the database from D1 since it's different than the DB made from the sqlite file

BBilly Right, I need the database from D1 since it's different than the DB made from th...

Hello, I’m Allie!•3/19/24, 12:52 PM

The D1 Database is the

.sqlite

.sqlite

file, unless you are referring to a remote D1 Database?

HHello, I’m Allie!The D1 Database **is** the `.sqlite` file, unless you are referring to a remote ...

Billy•3/19/24, 12:54 PM

Initially that is true but updates are made to the D1. I was hoping to get the updated DB from D1 out into a .sql

Billy•3/19/24, 12:55 PM

This is all local btw. I'd love the ability to get the remote data pulled down into a . sql as well if that were possible

Billy•3/19/24, 12:56 PM

The docs state there's no way to get a backup per se

BBilly Initially that is true but updates are made to the D1. I was hoping to get the u...

Hello, I’m Allie!•3/19/24, 12:56 PM

When those updates are made, they are made to the

.sqlite

.sqlite

file. D1 in local development is just a wrapper around that

.sqlite

.sqlite

file

BBilly This is all local btw. I'd love the ability to get the remote data pulled down ...

Hello, I’m Allie!•3/19/24, 12:56 PM

To dump a remote database, you can use https://github.com/nora-soderlund/cloudflare-d1-backups

GitHub

GitHub - nora-soderlund/cloudflare-d1-backups: A package to dump a ...

A package to dump a copy of your experimental D1 database through a worker. - nora-soderlund/cloudflare-d1-backups

HHello, I’m Allie!When those updates are made, they are made to the `.sqlite` file. D1 in local de...

Billy•3/19/24, 12:59 PM

so I can find that sqlite file in the

.wrangler

.wrangler

directory?

BBilly so I can find that sqlite file in the `.wrangler` directory?

Hello, I’m Allie!•3/19/24, 1:00 PM

That is correct

HHello, I’m Allie!That is correct

Billy•3/19/24, 1:01 PM

gotcha, I'll open each of those and see which one has the updates and then I can dump it for sure. Thank you!

Billy•3/19/24, 1:33 PM

Thanks for all the help, I'm rolling again locally. Have an awesome week

Matt Silverlock•3/19/24, 3:49 PM

The wonderful @gift-egwuenu built a full-stack demo application using D1, HonoX, and Cloudflare Pages called Staff Directory: https://github.com/lauragift21/staff-directory

GitHub

GitHub - lauragift21/staff-directory: an intuitive resource hub des...

an intuitive resource hub designed to showcase the teams within an organization. - lauragift21/staff-directory

MMatt Silverlock The wonderful @gift-egwuenu built a full-stack demo application using D1, HonoX,...

Matt Silverlock•3/19/24, 3:50 PM

You can see it live here: https://staff-directory-4to.pages.dev/

and the D1 specific / database handlers defined here: https://github.com/lauragift21/staff-directory/blob/main/app/db.ts

Mmare arcis Use a worker to import property listings into D1 from central source on a cadenc...

Max (@rozenmd)•3/19/24, 8:48 PM

are you using db.batch?

trogdor•3/20/24, 12:22 AM

db.exec

db.exec

disabled inside pages functions? Works fine locally with wrangler, but not after deployed.

Mmatt anyone here working on the drizzle d1 plugin, or is that the drizzle team workin...

trogdor•3/20/24, 12:53 AM

When you see you can't access

.exec

.exec

, do you get a

db.exec is not a function

db.exec is not a function

error? I'm getting that, wondering if it's the same thing you are seeing and if you found a workaround?

Ttrogdor When you see you can't access `.exec`, do you get a `db.exec is not a function` ...

matt•3/20/24, 1:09 AM

that was over a week ago, you're testing my memory

I think what I meant was that the drizzle API doesn't provide a way to access the

D1Database.exec

D1Database.exec

method

matt•3/20/24, 1:14 AM

here's the relevant code, which only calls into

.prepare()

.prepare()

https://github.com/drizzle-team/drizzle-orm/blob/main/drizzle-orm/src/d1/session.ts

nd the migrator tries to use the base sqlite-core dialect, it uses transactions which aren't supported by d1 : https://github.com/drizzle-team/drizzle-orm/blob/main/drizzle-orm/src/sqlite-core/dialect.ts#L768-L812

matt•3/20/24, 1:19 AM

but then again you're probably not running migrations inside the worker itself, so maybe that's why they haven't built out a migration story for that. the 000N files in the migrations folder should be compatible if you want to use wrangler to run your migrations

kumbag•3/20/24, 11:54 AM

hey! can I view my d1 database in dbeaver or a similar platform? or is it only available with the cli?

Kkumbag hey! can I view my d1 database in dbeaver or a similar platform? or is it only ...

Sam•3/20/24, 12:14 PM

I'm using https://dataflare.app

Dataflare

Dataflare - A simple, easy-to-use database manager

Easily connect to your Cloudflare D1, CockroachDB, libSQL, MariaDB, MySQL, PostgreSQL, Rqlite, SQLCipher, SQLite, SQL Server databases in Dataflare, manage Table, view Data, write SQL and run Query.

Jason Hostetter•3/20/24, 12:37 PM

Given the max row size of 1MB, is there a good pattern for breaking a large blob or JSON string across multiple rows if larger than 1MB? Reconfiguring all my statements to handle this (rare) situation seems painful. Best to just fail/reject in that case?

JJason Hostetter Given the max row size of 1MB, is there a good pattern for breaking a large blob...

Matt Silverlock•3/20/24, 12:52 PM

How large are your blobs? You could also write to R2 and reference from D1 - especially for large large blobs / multi MB blobs. No different from an image or binary data in that way.

Jason Hostetter•3/20/24, 12:57 PM

Yeah the issue is I guess it's technically unbounded. Vast majority are fairly small, but some object types can be very big. I have a mechanism for storing large data in R2 with a reference for other columns so I think that is probably the best solution here too. Just wanted to make sure there wasn't some other pattern to take advantage of that would preserve JSON queryability.

JJason Hostetter Yeah the issue is I guess it's technically unbounded. Vast majority are fairly s...

Matt Silverlock•3/20/24, 1:13 PM

You could always split across multiple rows - you’ll eat some query and insert complexity but you can still use JSON functions across rows.

jordan•3/20/24, 1:24 PM

Just working on a little prototype / test with SvelteKit + D1.

Trying out the REST API on a test database (1 row / col)

import { json } from "@sveltejs/kit";
import { ACCOUNT_ID, CLOUDFLARE_API_KEY, CLOUDFLARE_EMAIL, DATABASE_ID } from '$lib/server/secrets.js';

/** @type {import('./$types').RequestHandler} */
export async function GET({ platform }) {
  const url = `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/d1/database/${DATABASE_ID}/query`;
  const options = {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      'X-Auth-Email': CLOUDFLARE_EMAIL,
      'X-Auth-Key': CLOUDFLARE_API_KEY
    },
    body: '{"sql":"SELECT * from test"}'
  };
  const resp = await fetch(url, options);
  const data = await resp.json();
  return json(data);
}

import { json } from "@sveltejs/kit";
import { ACCOUNT_ID, CLOUDFLARE_API_KEY, CLOUDFLARE_EMAIL, DATABASE_ID } from '$lib/server/secrets.js';

/** @type {import('./$types').RequestHandler} */
export async function GET({ platform }) {
  const url = `https://api.cloudflare.com/client/v4/accounts/${ACCOUNT_ID}/d1/database/${DATABASE_ID}/query`;
  const options = {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      'X-Auth-Email': CLOUDFLARE_EMAIL,
      'X-Auth-Key': CLOUDFLARE_API_KEY
    },
    body: '{"sql":"SELECT * from test"}'
  };
  const resp = await fetch(url, options);
  const data = await resp.json();
  return json(data);
}

I can't get this query to run fast at all. Am I overlooking somemthing silly (an index)? The live endpoint won't run faster than 300ms

I see scale to zero is offered with D1. Does that mean the database spins down / goes to sleep after

Similar Threads

Similar Threads

Similar Threads