`Network connection lost.` in particular is the error a DO client throws when it disconnects from th

MMax (@rozenmd)`Network connection lost.` in particular is the error a DO client throws when it...

H

Hannes•6/6/24, 12:38 PM

Ok, thanks. Unsure how to implement that, though, as requests are handled entirely by prisma. I'll see if I open an issue over there.
Is that expected, though, or is it an error that you're monitoring and expecting to improve?

HHannes Ok, thanks. Unsure how to implement that, though, as requests are handled entire...

M

Max (@rozenmd)OP•6/6/24, 6:09 PM

I'd probably wrap your prisma calls in a try/catch (if its throwing an error) and try again - we're monitoring all errors and will find fixes for them over time

MMax (@rozenmd)I'd probably wrap your prisma calls in a try/catch (if its throwing an error) an...

H

Hannes•6/6/24, 6:13 PM

Thanks for the info. My application more than 1000 prisma calls, so that'd probably have to be a more generic approach

But great to know that you're monitoring this.

F

Foywards Bound•6/6/24, 11:44 PM

Is there a best practice around primary keys / auto incrementing ids in D1?

B

berniesumption•6/7/24, 8:58 AM

To flesh out Alexander's answer a bit, since we're using SQLite, every row will have an auto-incrementing ID by default. If you define your own

INTEGER PRIMARY KEY

INTEGER PRIMARY KEY

INTEGER PRIMARY KEY

INTEGER PRIMARY KEY column, that's the auto-incrementing ID. If you don't, you'll get a default one called

ROWID

ROWID

that you can use for queries. You can opt out by defining the table as

WITHOUT ROWID

WITHOUT ROWID

WITHOUT ROWID

WITHOUT ROWID but that comes with some additional constraints - https://sqlite.org/withoutrowid.html - and you should only do that if you know what you're doing.

So SQLite, and D1, support auto-incrementing IDs just fine.

Separately, there are all kinds of reasons why UUIDs are preferable to auto-incrementing IDs for most apps regardless of the database engine. So it is good advice to use UUIDs by default unless you have a good reason to use auto-incrementing integers and understand the potential pitfalls with them (e.g. enabling id enumeration attacks and leaking information about the size of tables).

J

jepcd•6/7/24, 9:15 AM

Hi, is there a limit on the number of statements in a batch call?

G

Gerbuuun•6/7/24, 9:31 AM

I use auto incrementing IDs for internal use (server and joins) and have a nanoid which is used by users

Original message was deleted

B

berniesumption•6/7/24, 9:31 AM

Yes ULIDs are great - provided that you don't mind leaking the creation time of every entity that you expose the ID of. They look nicer too

Also, I like to prefix my IDs with a short version of the table name, e.g. an employee might be

emp01FHZXHK8PTP9FVK99Z66GXQTX

emp01FHZXHK8PTP9FVK99Z66GXQTX

emp01FHZXHK8PTP9FVK99Z66GXQTX

emp01FHZXHK8PTP9FVK99Z66GXQTX. I took that idea from Stripe, it makes it so much easier to debug when you have random IDs being passed around.

Jjepcd Hi, is there a limit on the number of statements in a batch call?

M

Max (@rozenmd)OP•6/7/24, 9:55 AM

how ever many queries you can fit before running out of memory

M

Max (@rozenmd)OP•6/7/24, 9:56 AM

I've seen 100k queries in a batch

Jjepcd Hi, is there a limit on the number of statements in a batch call?

N

notjoemartinez•6/8/24, 7:21 AM

The docs are a bit vague on this. I've done about 30k at once, the limit was that the query needs to run in under 30 seconds and I accomplished this by removing some triggers that were slowing it down. I think you still need to consider the number of bindings depending on if they are counted within the batch call. The upper limit for bindings is "approximately" 25 million.

Nnotjoemartinez The docs are a bit vague on this. I've done about 30k at once, the limit was tha...

H

Hello, I’m Allie!•6/8/24, 7:24 AM

As you noted, the binding itself doesn’t place any limits on the number of statements, so the only actual limit is however many you can fit in memory, and that they are created before you overrun the CPU time limit

S

Singer•6/8/24, 9:46 AM

There's probably layers to this question but: D1 or supabase

SSinger There's probably layers to this question but: D1 or supabase

H

Hello, I’m Allie!•6/8/24, 9:51 AM

How big is your app? What kind of data are you storing? How many reads/writes are you doing?

HHello, I’m Allie!How big is your app? What kind of data are you storing? How many reads/writes ar...

S

Singer•6/8/24, 9:58 AM

I'm very new to backend developement and I'm taking things as they come. I'm not sure how big the app is going to get, but I need tables for users, weather data, news api data, events(id,date,actors involved, description, location, image blobs....)

I want to use workers AI which is why I was leaning towards d1 for better integration but I read somewhere that sqlite isn't great for handling lots of data. Again I'm not sure how big this thing can get and I'm fairly new to this realm . A tl;dr or any resources that I can use to improve my knowledge would be great

SSinger I'm very new to backend developement and I'm taking things as they come. I'm not...

H

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

D1 should be fine? Though for larger datasets, I would probably go with Supabase

SSinger I'm very new to backend developement and I'm taking things as they come. I'm not...

M

maj•6/8/24, 12:08 PM

Whatever "handling lots of data" means. Are you talking about millions of records or more? I'm working on an application which has users with > 1M records in a single table, with many relations to other tables. And it's working perfectly fine on a regular Windows PC using SQLite. I'd expect d1 to perform even better.

M

Michał Wróblewski•6/8/24, 1:08 PM

will it be ever possible to do ATTACH DATABASE on D1? It would be great to split some DBs but be able to query them together

HHello, I’m Allie!D1 should be fine? Though for larger datasets, I would probably go with Supabase

S

Singer•6/8/24, 4:09 PM

Thanks, just don't want to get to a point in the near future where I regret going with d1 or sqlite but I don't think I'd reach 1m anytime soon so that's great. Thanks again for the clarity @maj @Hello, I’m Allie!

I

Iaci•6/8/24, 9:56 PM

hi all, i'm developing a worker that has access to D1 databases through D1 database bindings (set as variables under D1 Database Bindings). how am i able to reach those databases when i'm developing locally? using queries like this: {results} = await env.IRADB.prepare(<here goes the query>).bind(<binds>).run();

M

Murder Chicken•6/8/24, 9:58 PM

Is it possible to request an increase in the column limit of 100? If so, what's the best route to do that on the Worker Paid plan?

M

Murder Chicken•6/8/24, 10:03 PM

Never mind, found the limit increase form!

MMurder Chicken Is it possible to request an increase in the column limit of 100? If so, what's...

B

bun•6/9/24, 12:52 AM

bro for what possibly you have 100+ columns if i may ask

M

Murder Chicken•6/9/24, 2:18 PM

I'd like to work with a different table model for a storing calendar availability data.

M

Murder Chicken•6/9/24, 2:20 PM

As sqlite doesn't offer

pivot

pivot

pivot

pivot or

crosstab

crosstab

crosstab

crosstab queries, calendar querying (for the type of data I'm dealing with) is very complex. I'd like to try a different approach. One column per day per resource with the value of the availability stored as a

tinyint

tinyint

tinyint

tinyint.

Q

quisi.do•6/9/24, 5:20 PM

Is it realistic to run 2 queries per request? I'm wanting to query something like

SELECT id FROM projects WHERE url = ?

SELECT id FROM projects WHERE url = ?

SELECT id FROM projects WHERE url = ?

SELECT id FROM projects WHERE url = ? then

SELECT something FROM metadata WHERE id = ?

SELECT something FROM metadata WHERE id = ?

SELECT something FROM metadata WHERE id = ?

SELECT something FROM metadata WHERE id = ? using that ID (where there could be multiple

something

something

s in the latter table).
I'm worried this design may bottleneck me. My last experience with databases was PHP/MySQL era, and the sheer number of queries ran on pageload was the most common bottleneck for me back then. Is this an acceptable pattern?

A

AmaraFray•6/9/24, 8:06 PM

has anyone tried to make dynamic tables

i have multiple organisations (A,B,C,D) part of my application, with each having tables 1-10

so each table is A1,A2,A3.. and so on. I want 1-10 to have the same structure (is it possible to template, like using the 'like' operator in sql)

or is there a better approach, I could merge it all into one, but I'd rather not as each is distributed to a different place, and i want it to be optimised like that

A

AmaraFray•6/9/24, 8:07 PM

and if you have, any chance u can suggest your orm structure too

Qquisi.do Is it realistic to run 2 queries per request? I'm wanting to query something lik...

I

IEatBeans•6/9/24, 10:42 PM

Could you use joins instead of 2 separate queries? You may be able to use batch as well, though I’m not sure because you are using the Id from the first one in the second one.

Either way, D1 is really fast and many of my routes involve 3-5 queries (most batched)

D

dpkp•6/10/24, 1:00 AM

what's the best way to drop a local d1 db? I looked around for commands but didn't find any docs. I ended up manually finding and removing sqlite files in .wrangler/state/v3/d1 ...

P

predaytor•6/10/24, 7:38 AM

Does D1 support transactions? Seems like not:

To execute a transaction, please use the state.storage.transaction() API instead of the SQL BEGIN TRANSACTION or SAVEPOINT statements. The JavaScript API is safer because it will automatically roll back on exceptions, and because it interacts correctly with Durable Objects' automatic atomic write coalescing.
Error: D1_ERROR: not authorized
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

To execute a transaction, please use the state.storage.transaction() API instead of the SQL BEGIN TRANSACTION or SAVEPOINT statements. The JavaScript API is safer because it will automatically roll back on exceptions, and because it interacts correctly with Durable Objects' automatic atomic write coalescing.
Error: D1_ERROR: not authorized
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

To execute a transaction, please use the state.storage.transaction() API instead of the SQL BEGIN TRANSACTION or SAVEPOINT statements. The JavaScript API is safer because it will automatically roll back on exceptions, and because it interacts correctly with Durable Objects' automatic atomic write coalescing.
Error: D1_ERROR: not authorized
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

To execute a transaction, please use the state.storage.transaction() API instead of the SQL BEGIN TRANSACTION or SAVEPOINT statements. The JavaScript API is safer because it will automatically roll back on exceptions, and because it interacts correctly with Durable Objects' automatic atomic write coalescing.
Error: D1_ERROR: not authorized
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

몰

몰라세스•6/10/24, 7:38 AM

not supported? maybe.

Ppredaytor Does D1 support transactions? Seems like not: ```bash To execute a transaction, ...

H

Hello, I’m Allie!•6/10/24, 9:04 AM

All queries/batches are run within transactions,but you can’t manually create your own

P

predaytor•6/10/24, 11:21 AM

what is the correct way to store a reference to an uploaded cloudflare r2 image in the database? save id of the uploaded image, and then somehow get the necessary data such as width/height and other metadata (causing waterfalls?) or save the data during upload directly to the separate table, for example:

export const user = sqliteTable('user', {
    id: integer('id').notNull().primaryKey(),
    avatarId: text('avatar_id', { mode: 'text', length: 255 }),
});

export const user = sqliteTable('user', {
    id: integer('id').notNull().primaryKey(),
    avatarId: text('avatar_id', { mode: 'text', length: 255 }),
});

export const user = sqliteTable('user', {
    id: integer('id').notNull().primaryKey(),
    avatarId: text('avatar_id', { mode: 'text', length: 255 }),
});

export const user = sqliteTable('user', {
    id: integer('id').notNull().primaryKey(),
    avatarId: text('avatar_id', { mode: 'text', length: 255 }),
});

vs

export const user = sqliteTable('user', {
    id: integer('id').notNull().primaryKey(),
    avatarId: integer('avatar_id').references(() => media.id, { onDelete: 'set null' }),
});

// ...

export const media = sqliteTable('media', {
    id: integer('id').notNull().primaryKey(),
    createdAt: integer('created_at', { mode: 'timestamp' })
        .notNull()
        .default(sql`(unixepoch())`),
    updatedAt: integer('updated_at', { mode: 'timestamp' })
        .notNull()
        .default(sql`(unixepoch())`),
    fileName: text('file_name', { mode: 'text', length: 255 }).notNull(),
    mediaType: text('file_type', { mode: 'text' }).notNull(),
    mimeType: text('mime_type', { mode: 'text', length: 100 }).notNull(),
    size: integer('size', { mode: 'number' }).notNull(),
    width: integer('width', { mode: 'number' }).notNull(),
    height: integer('height', { mode: 'number' }).notNull(),
    src: text('src', { mode: 'text' }).notNull(),
    srcSet: text('srcset').notNull(),
    alt: text('alt', { mode: 'text' }).notNull(),
});

export const user = sqliteTable('user', {
    id: integer('id').notNull().primaryKey(),
    avatarId: integer('avatar_id').references(() => media.id, { onDelete: 'set null' }),
});

// ...

export const media = sqliteTable('media', {
    id: integer('id').notNull().primaryKey(),
    createdAt: integer('created_at', { mode: 'timestamp' })
        .notNull()
        .default(sql`(unixepoch())`),
    updatedAt: integer('updated_at', { mode: 'timestamp' })
        .notNull()
        .default(sql`(unixepoch())`),
    fileName: text('file_name', { mode: 'text', length: 255 }).notNull(),
    mediaType: text('file_type', { mode: 'text' }).notNull(),
    mimeType: text('mime_type', { mode: 'text', length: 100 }).notNull(),
    size: integer('size', { mode: 'number' }).notNull(),
    width: integer('width', { mode: 'number' }).notNull(),
    height: integer('height', { mode: 'number' }).notNull(),
    src: text('src', { mode: 'text' }).notNull(),
    srcSet: text('srcset').notNull(),
    alt: text('alt', { mode: 'text' }).notNull(),
});

export const user = sqliteTable('user', {
    id: integer('id').notNull().primaryKey(),
    avatarId: integer('avatar_id').references(() => media.id, { onDelete: 'set null' }),
});

// ...

export const media = sqliteTable('media', {
    id: integer('id').notNull().primaryKey(),
    createdAt: integer('created_at', { mode: 'timestamp' })
        .notNull()
        .default(sql`(unixepoch())`),
    updatedAt: integer('updated_at', { mode: 'timestamp' })
        .notNull()
        .default(sql`(unixepoch())`),
    fileName: text('file_name', { mode: 'text', length: 255 }).notNull(),
    mediaType: text('file_type', { mode: 'text' }).notNull(),
    mimeType: text('mime_type', { mode: 'text', length: 100 }).notNull(),
    size: integer('size', { mode: 'number' }).notNull(),
    width: integer('width', { mode: 'number' }).notNull(),
    height: integer('height', { mode: 'number' }).notNull(),
    src: text('src', { mode: 'text' }).notNull(),
    srcSet: text('srcset').notNull(),
    alt: text('alt', { mode: 'text' }).notNull(),
});

export const user = sqliteTable('user', {
    id: integer('id').notNull().primaryKey(),
    avatarId: integer('avatar_id').references(() => media.id, { onDelete: 'set null' }),
});

// ...

export const media = sqliteTable('media', {
    id: integer('id').notNull().primaryKey(),
    createdAt: integer('created_at', { mode: 'timestamp' })
        .notNull()
        .default(sql`(unixepoch())`),
    updatedAt: integer('updated_at', { mode: 'timestamp' })
        .notNull()
        .default(sql`(unixepoch())`),
    fileName: text('file_name', { mode: 'text', length: 255 }).notNull(),
    mediaType: text('file_type', { mode: 'text' }).notNull(),
    mimeType: text('mime_type', { mode: 'text', length: 100 }).notNull(),
    size: integer('size', { mode: 'number' }).notNull(),
    width: integer('width', { mode: 'number' }).notNull(),
    height: integer('height', { mode: 'number' }).notNull(),
    src: text('src', { mode: 'text' }).notNull(),
    srcSet: text('srcset').notNull(),
    alt: text('alt', { mode: 'text' }).notNull(),
});

J

JoeDoe•6/10/24, 6:42 PM

how to cache d1 requests?

J

JoeDoe•6/10/24, 6:42 PM

I'm using workers for a web api, but I need simple data like total users to be cached for like 60seconds or similiar

JJoeDoe how to cache d1 requests?

U

Unsmart•6/10/24, 6:57 PM

the cache api https://developers.cloudflare.com/workers/runtime-apis/cache/

UUnsmart the cache api <https://developers.cloudflare.com/workers/runtime-apis/cache/>

J

JoeDoe•6/10/24, 7:05 PM

is there some good examples on how to use this with workers?

JJoeDoe is there some good examples on how to use this with workers?

M

Max (@rozenmd)OP•6/10/24, 7:14 PM

https://developers.cloudflare.com/workers/examples/cache-api/

Cloudflare Docs

Using the Cache API · Cloudflare Workers docs

Documentation for Cloudflare Workers, a serverless execution environment that allows you to create entirely new applications or augment existing ones …

J

JoeDoe•6/10/24, 7:21 PM

hmmmmm interesting thank you

M

maj•6/10/24, 10:45 PM

FWIW: I'm using KV to cache some query results I'd like to share across requests. The Cache API would only cache the result of HTTP requests, wouldn't it?

U

Unsmart•6/10/24, 11:06 PM

The cache api can cache anything... normal http requests you can cache with just the fetch api

M

maj•6/11/24, 4:45 AM

Maybe I'm missing the obvious, but you have to pass it a response object, with caching headers set etc. How would I define the expiration if I wanted to cache a random blob?

M

maj•6/11/24, 4:46 AM

From https://developers.cloudflare.com/workers/reference/how-the-cache-works/#cache-api:

The Cache API can be thought of as an ephemeral key-value store, whereby the Request object (or more specifically, the request URL) is the key, and the Response is the value.

Cloudflare Docs

How the Cache works · Cloudflare Workers docs

How Workers interacts with the Cloudflare cache.

Mmaj From https://developers.cloudflare.com/workers/reference/how-the-cache-works/#ca...

M

Max (@rozenmd)OP•6/11/24, 7:21 AM

make a new Response, put your blob in the body

MMax (@rozenmd)make a new Response, put your blob in the body

M

maj•6/11/24, 7:30 AM

My comment was in response to use @Unsmart | Tech debt claiming that the Cache API could cache anything. But you basically confirm that I can't cache the blob alone (because I want to reuse it in other handlers), don't you? Using the Cache API I can only cache the full response?

Mmaj My comment was in response to use @Unsmart | Tech debt claiming that the Cache A...

H

Hello, I’m Allie!•6/11/24, 7:39 AM

Well no? You create a new, completely separate Response, that is just the blob+cache headers. That Response is never served to the client, it is just used to interact with the Cache API

HHello, I’m Allie!Well no? You create a new, completely separate Response, that is just the blob+c...

M

maj•6/11/24, 9:15 AM

It's not a general purpose cache, is it? It's based on HTTP requests and responses. Even if you provide a random string as the cache key "it is interpreted as the URL for a new Request object." (https://developers.cloudflare.com/workers/runtime-apis/cache/). So in order to cache the raw result of a d1 query I'd have to wrap and unwrap the result. This only adds complexity and overhead, and still doesn't provide a global cache like using KV does. The original question was "how to cache d1 requests?". Not "how to cache http requests".

`Network connection lost.` in particular is the error a DO client throws when it disconnects from th

Similar Threads

Similar Threads

Similar Threads