Changelog going out soon, but for those here: * D1's `.raw()`, `.all()` and `.run()` query statemen

Changelog going out soon, but for those here:

D1's
```
.raw()
```
```
.raw()
```
,
```
.all()
```
```
.all()
```
and
```
.run()
```
```
.run()
```
query statement methods (https://developers.cloudflare.com/d1/build-databases/query-databases/#query-statement-methods) have been updated to reflect their intended behaviour and improving compatibility with ORMs.
```
.raw()
```
```
.raw()
```
now correctly returns results an array of arrays, allowing the correct handling of duplicate column names (such as when joining tables), as compared to
```
.all()
```
```
.all()
```
, which is unchanged and returns an array of objects. To include an array of column names in the results when using
```
.raw()
```
```
.raw()
```
, use
```
.raw({columnNames: true})
```
```
.raw({columnNames: true})
```
.
```
.run()
```
```
.run()
```
no longer incorrectly returns a
```
D1Result
```
```
D1Result
```
and instead returns a
```
D1ExecResult
```
```
D1ExecResult
```
(https://developers.cloudflare.com/d1/build-databases/query-databases/#return-object) as originally intended and documented.

This may be a breaking change for some applications that expected

.raw()

.raw()

to return an array of objects.

MMatt Silverlock Changelog going out soon, but for those here: * D1's `.raw()`, `.all()` and `.r...

kev-ac•2/14/24, 1:56 AM

It was indeed a breaking change for us, even if it was never intended to work that way. Replacing the .run() with .all() seemed to have done the trick for now. Back to sleep

Unsmart•2/14/24, 1:57 AM

That’s what a betas for tho

Jadugar_Jaggu•2/14/24, 4:05 AM

beeeetaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

ZZiga Zajc Multiple statements in a single query are not supported?

Unsmart•2/14/24, 4:19 AM

https://developers.cloudflare.com/d1/build-databases/query-databases/#batch-statements

Kkev-ac It was indeed a breaking change for us, even if it was never intended to work th...

conneo•2/14/24, 7:48 AM

Same for us. .all() seems to fix the problem

Kkev-ac It was indeed a breaking change for us, even if it was never intended to work th...

conneo•2/14/24, 7:50 AM

On top of that doc the .run() is mentioned as responding with results array, that's somewhat confusing. On the details section for .run() it's correctly mentioned that there are no results in response

sultan.xh•2/14/24, 7:54 AM

Is anyone having an issue with D1? It looks like it is failing to return results.

sultan.xh•2/14/24, 7:55 AM

A basic simple select query does not return any result array.

Kyrre•2/14/24, 7:57 AM

Same issue here @sultan.xh.

sultan.xh•2/14/24, 7:58 AM

Yes, the Return object is missing results.

Nehal Ali•2/14/24, 7:59 AM

@sultan.xh if you are using .run() it is now won't be returning any results

sultan.xh•2/14/24, 7:59 AM

What should I use then?

Nehal Ali•2/14/24, 7:59 AM

@sultan.xh .all() instead

sultan.xh•2/14/24, 8:00 AM

Okay, it is a small change, but it has a big impact. I need to modify everything now.

sultan.xh•2/14/24, 8:00 AM

Thanks!

UUnsmart That’s what a betas for tho 🤝

kev-ac•2/14/24, 8:42 AM

I never said that I was unaware of its beta state. Noticed the issue, changed it in code, be done with it

Max (@rozenmd)•2/14/24, 9:04 AM

@D1 Database PSA: if you are using

.run()

.run()

and expecting it to return results, you should be using

.all()

.all()

: d1-database

shahzaibkhalid•2/14/24, 9:20 AM

Does anyone know if Prisma works with D1?

Sshahzaibkhalid Does anyone know if Prisma works with D1?

bun•2/14/24, 9:24 AM

https://github.com/prisma/prisma/issues/13310 nope

GitHub

Support for Cloudflare's new SQLite database D1 · Issue #13310 · pr...

Cloudflare have just announced their first relational DB D1 which is based on SQLite. https://blog.cloudflare.com/introducing-d1/ Would be awesome if Prisma could support it one day..

Sshahzaibkhalid Does anyone know if Prisma works with D1?

Asher•2/14/24, 11:21 AM

Only DrizzleORM for now

MMatt Silverlock Changelog going out soon, but for those here: * D1's `.raw()`, `.all()` and `.r...

Matt SilverlockOP•2/14/24, 11:39 AM

Official change-log and updated documentation for breaking changes to

all()

all()

raw()

raw()

and

first()

first()

https://developers.cloudflare.com/d1/platform/changelog/#2024-02-13

Cloudflare Docs

Changelog · Cloudflare D1 docs

D1’s raw(), all() and run() query statement methods have been updated to reflect their intended behaviour and improve compatibility with ORMs …

Kkev-ac I never said that I was unaware of its beta state. Noticed the issue, changed it...

Unsmart•2/14/24, 12:37 PM

Sorry that comment wasn’t directed at you just the change

Ɽ

ⱤØ₥₳₦•2/14/24, 2:44 PM

How to predefine location for D1

ⱤⱤØ₥₳₦How to predefine location for D1

Matt SilverlockOP•2/14/24, 2:48 PM

https://developers.cloudflare.com/d1/configuration/data-location/

Cloudflare Docs

Data location · Cloudflare D1 docs

Learn how the location of data stored in D1 is determined, including where the leader is placed and how you optimize that location based on your …

Ian•2/14/24, 2:54 PM

will dynamic binding be part of GA release by April ?

MMax (@rozenmd).sqlite export is being specced out but is unlikely to arrive within the month, ...

Luka•2/14/24, 2:58 PM

Unfortunately I keep hitting the limits either memory/max execution time or sub requests. I opened ticket at cloudflare if they can lift the limits but pretty much it always errors out with no information. I really feel hopeless on that one other than manually transferring the rows.

If you would feel kind enough to look through and share any ideas on the issue, I'd really appreciate that!
https://github.com/nora-soderlund/cloudflare-d1-backups/issues/9

GitHub

Errors: Http 500 - CF 1101 // Http 503 - CF 1105 // Http 504 · Issu...

Hi again. I'm back at it once again trying to export a 450 MB-large database. My own worker uses Hono and I would constantly see the Inspector command exceeded memory limits errors. I've de...

MMatt Silverlock https://developers.cloudflare.com/d1/configuration/data-location/

Ɽ

ⱤØ₥₳₦•2/14/24, 3:13 PM

Dayum, now I'm legally blind

. Thanks for the resource

Original message was deleted

Max (@rozenmd)•2/14/24, 3:22 PM

+1 to deploying it,

wrangler dev

wrangler dev

's Workers !== real Workers

Original message was deleted

Luka•2/14/24, 3:57 PM

Yes

Original message was deleted

Luka•2/14/24, 3:58 PM

That's great. But there's this one table that has around 90k rows and I suspect it being a few hundred MBs

MMax (@rozenmd)+1 to deploying it, `wrangler dev`'s Workers !== real Workers

Luka•2/14/24, 3:59 PM

to remove any ambiguity, are you talking about

worker dev --remote

worker dev --remote

LLuka to remove any ambiguity, are you talking about `worker dev --remote`? 🙂

Max (@rozenmd)•2/14/24, 3:59 PM

yes

MMax (@rozenmd)yes

Luka•2/14/24, 3:59 PM

so you're suggesting that deployed worker has higher limits?

Luka•2/14/24, 4:00 PM

Haha, I did that, Nora. I got same errors. But I am, nevertheless, curious to learn how much different they are

Max (@rozenmd)•2/14/24, 4:05 PM

the Worker that runs when you run

wrangler dev --remote

wrangler dev --remote

doesn't have the same performance characteristics as a deployed Worker (which runs across Cloudflare's network)

Original message was deleted

Luka•2/14/24, 4:17 PM

I think it worked! It took 3 minutes for ~550MB and ~115k rows. Gonna test on local sqlite now

Luka•2/14/24, 4:27 PM

It seems to be OK! Thank youuuu so much man. I have no idea how to express how much stress you lifted from me, @Alexandеr . Thank you for it. I think you also deserve updating your README.mdREADME.md that it can potentially handle big DBs.

I will make PR later to Cloudflare docs if it's not there yet amongst other community tools.

And thank you Nora for your willingness and support along the way. It takes a great deal to maintain the package.

Sébastien Morel•2/14/24, 5:42 PM

hello here,this change about .run.run I have updated the types and wrangler and I still see that

run

run

returns a D1Response. What I am missing?

Santosh•2/14/24, 7:32 PM

When I start wrangler dev, I am not able to resolve a table that I have created by using a local command this way:

 wrangler d1 execute TestDB --local --file=./sql/sequence.sql

 wrangler d1 execute TestDB --local --file=./sql/sequence.sql

Uncaught (async) Error: D1_ERROR: SqliteError: no such table:

Uncaught (async) Error: D1_ERROR: SqliteError: no such table:

Santosh•2/14/24, 7:33 PM

What could I be doing wrong? Would I have to tell wrangler something abut using my local db ?

Santosh•2/14/24, 7:36 PM

I even ran a pragma and I could the fields of the table. When I start wrangler, it even shows my test db:

- D1 Databases:
  - DB: TestDB (c73a0***-

- D1 Databases:
  - DB: TestDB (c73a0***-

Santosh•2/14/24, 9:05 PM

const table = new Model(
{
D1Orm: orm,
tableName: "MyTableName",
primaryKeys: "id",
},

Santosh•2/14/24, 9:06 PM

Using the orm tool

Santosh•2/14/24, 9:09 PM

Is there a concept of preview_database_id that I need to mention inside wrangler? If so, how do I get it?

Santosh•2/14/24, 9:15 PM

Same with env.DB.exec("SELECT * FROM MyTableName");

Changelog going out soon, but for those here: * D1's `.raw()`, `.all()` and `.run()` query statemen

Similar Threads

Similar Threads

Similar Threads