That is correct

HHello, I’m Allie!That is correct

B

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!

B

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

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

M

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,...

M

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...

M

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

are you using db.batch?

T

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

Is

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...

T

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` ...

M

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

M

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

M

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

K

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 ...

S

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.

J

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...

M

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.

J

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...

M

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.

J

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);
}

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

J

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

Oh geez. I found this:

D1's REST API doesn't involve a Worker, which is why it's considerably slower

D1's REST API doesn't involve a Worker, which is why it's considerably slower

above in the chat. Oy vey.

J

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

The dev experience for SK + D1 was rough, so I tried this route. I'll try again. https://developers.cloudflare.com/d1/examples/d1-and-sveltekit/

P

Prisma Gestión Empresarial•3/20/24, 2:26 PM

did the migrations script break for anyone? I got a github action that always runs

d1 migrations apply <DB>

d1 migrations apply <DB>

and it always did a check to see if there where any new migrations to apply and applied them (if none, then did nothing).

but since my last commit ~30 mins ago, it started applying them all over again (not just the new ones)

SSam I'm using https://dataflare.app

P

Patrick•3/20/24, 2:28 PM

Ah cool I was looking for a lightweight one of these, any idea if there's anything similar to drizzle-kit studio that can be npm installed and used directly from the project?

V

vnphanquang•3/21/24, 5:25 AM

Hi all, is it safe to expose

database_id

database_id

in

wrangler.toml

wrangler.toml

in public repo? If no is there any convenient alternative rather than using a separate secret wrangler.toml? Thank you

D

down•3/21/24, 8:46 AM

Hi, is there any way to connect the d1 locally without a worker? I going to write a migration script with typescript. Thanks

Ddown Hi, is there any way to connect the d1 locally without a worker? I going to writ...

D

dakom•3/21/24, 9:08 AM

I think it's safe to just connect to the local sqlite files directly. By default they'll be somewhere in

.wrangler/state/...

.wrangler/state/...

but you can set the path explicitly when you start the worker with

--persist-to={path}

--persist-to={path}

Ddakom I _think_ it's safe to just connect to the local sqlite files directly. By defau...

D

down•3/21/24, 9:24 AM

Thanks i will try it

AAaronO @down You can usually do `wrangler d1 migrations apply <YOUR_DB> --local`, assum...

D

down•3/21/24, 9:56 AM

Thanks, but i have to connect the db to read and write back, not just import data

AAaronO @down Would that work ?

D

down•3/21/24, 10:59 AM

yes, direct access to .sqlite works and I'll probably make a temporary entry point for remote modifications, thanks.

S

squareclamp•3/21/24, 6:17 PM

I like how my queries are all 0ms

We should just remove the y-axis.

A

Amblamps•3/21/24, 7:49 PM

How does D1 handle concurrent access? Should we be using queues in front of it?

AAmblamps How does D1 handle concurrent access? Should we be using queues in front of it?

I

Isaac McFadyen•3/21/24, 7:53 PM

Concurrent access is completely fine.

I

Isaac McFadyen•3/21/24, 7:54 PM

It's like a normal SQLite database in that respect.

C

Chaika•3/21/24, 7:56 PM

It is, at least right now, a single threaded Durable Object so if you slam it too hard with writes you can kill it. It performs quite well though, idk what the upper limit would be, and it would depend on other factors too like what exactly you're writing

M

Max (@rozenmd)•3/21/24, 8:05 PM

is it a bug or are they under 1ms

Mmare arcis can you clarify "kill it"? DB corruption? extremely slowness until recovery?

C

Chaika•3/21/24, 8:07 PM

No corruption. From what I've seen, it just gets really slow/sometimes becomes overloaded and stops working for "a bit" until it fixes itself/writes slow down.

CChaika It is, at least right now, a single threaded Durable Object so if you slam it to...

S

Sam•3/21/24, 10:22 PM

What about reads. How many per second can it handle? About 20k people can open our app on a push notification. To that’s 20k queries in about 2-3 minutes.

Is D1 able to handle that? There aren’t any writes.

SSam What about reads. How many per second can it handle? About 20k people can open o...

M

Max (@rozenmd)•3/22/24, 7:53 AM

a single DO instance can do around 1k requests per second, for complicated queries i've seen it drop as low as 400 requests per second - if in doubt, use the cache api where possible

V

vakno•3/22/24, 10:04 AM

hello i need some help with indexes. Pretty new to this so sorry if this seems stupid.

i created table

  CREATE TABLE IF NOT EXISTS ProductData (
      id INTEGER PRIMARY KEY AUTOINCREMENT,
      url TEXT,
      price NUMBER,
      description TEXT
  )

  CREATE TABLE IF NOT EXISTS ProductData (
      id INTEGER PRIMARY KEY AUTOINCREMENT,
      url TEXT,
      price NUMBER,
      description TEXT
  )

  CREATE TABLE IF NOT EXISTS ProductData (
      id INTEGER PRIMARY KEY AUTOINCREMENT,
      url TEXT,
      price NUMBER,
      description TEXT
  )

  CREATE TABLE IF NOT EXISTS ProductData (
      id INTEGER PRIMARY KEY AUTOINCREMENT,
      url TEXT,
      price NUMBER,
      description TEXT
  )

then i created index

  'CREATE INDEX IF NOT EXISTS idx_url ON ProductData (price, description)'

  'CREATE INDEX IF NOT EXISTS idx_url ON ProductData (price, description)'

  'CREATE INDEX IF NOT EXISTS idx_url ON ProductData (price, description)'

  'CREATE INDEX IF NOT EXISTS idx_url ON ProductData (price, description)'

when i query table i get same numbers of row read as without index.

SELECT * FROM ProductData

SELECT * FROM ProductData

SELECT * FROM ProductData

SELECT * FROM ProductData

What am i doing wrong?

Vvakno hello i need some help with indexes. Pretty new to this so sorry if this seems s...

S

Sam•3/22/24, 10:27 AM

Because you’re not using a filter in the query. You’re basically requesting all rows with that query

SSam Because you’re not using a filter in the query. You’re basically requesting all ...

V

vakno•3/22/24, 10:38 AM

oh okay. Are there any other ways i can reduce rows read everytime route is triggered? Any caching systems?

Similar Threads