`json_each` - https://developers.cloudflare.com/d1/learning/querying-json/#supported-functions

MMatt Silverlock `json_each` - https://developers.cloudflare.com/d1/learning/querying-json/#suppo...

I

itsmatteomanf•8/31/23, 11:43 AM

Yeah, that one above worked

I didn’t think it returned the key, too. It works, it’s not the fastest but it’s 10s of keys on tens of thousands of rows

I

itsmatteomanf•8/31/23, 11:44 AM

@rozenmd adding to the request for indexes, maybe show views, too

E

Epailes•8/31/23, 12:10 PM

Are there any examples of a popular CMS setup with D1 yet?

EEpailes Are there any examples of a popular CMS setup with D1 yet?

C

Cyb3r-Jak3•8/31/23, 1:24 PM

I mean someone made a CMS on workers https://discord.com/channels/595317990191398933/783765338692386886/1133082793962909846

CCyb3r-Jak3 I mean someone made a CMS on workers https://discord.com/channels/59531799019139...

E

Epailes•8/31/23, 3:10 PM

Ooh I'd missed that post thanks for sharing!
Was mainly looking to see if there was a full CMS, not headless, but interesting read none the less!

U

Unsmart•8/31/23, 5:53 PM

It wont be removed just higher 100s of GBs. Can probably do a search and find the messages about it specifically

U

Unsmart•8/31/23, 5:57 PM

I mean D1 isnt a global db. Eventually it will have read regions sure but its single region writer so

U

Unsmart•8/31/23, 6:09 PM

Afaik eventually they are working on a thing that will allow dynamic creation of D1 similar to durable objects where you can do env.D1.get("table-id").query("SELECT something from 'my-table'"). But thats probably very long out goal

U

Unsmart•8/31/23, 6:10 PM

Would have to find that message where they said that

K

kian•8/31/23, 6:39 PM

None that Cloudflare provide

U

Unsmart•8/31/23, 6:46 PM

I mean even through all of those status pages I havent had any issues with anything I host on CF pages and I only had 1 request error to a service I use that uses cloudflare so

ZZiga Zajc Thanks, basically based on #cloudflare-status there is downtime almost every day...

D

DaniFoldi•8/31/23, 7:42 PM

that's true for most providers - the only difference is whether they sweep "small" outages under the rug, or still create an incident

G

giuseppelt•8/31/23, 11:43 PM

Is there some issue with the Pages binding? It stopped to work all the sudden

G

giuseppelt•8/31/23, 11:43 PM

The env key is missing, instead I see a strange

__D1_BETA__DB

__D1_BETA__DB

G

giuseppelt•8/31/23, 11:44 PM

Are you moving to beta, and something is mssing?

U

Unsmart•8/31/23, 11:44 PM

afaik D1 bindings have always been like that because of the alpha

G

giuseppelt•8/31/23, 11:44 PM

no

G

giuseppelt•8/31/23, 11:45 PM

if you named the binding DB, you'll get a DB key on the env

G

giuseppelt•8/31/23, 11:45 PM

it always worked, I found out it stopped, could be a couple of hours, maybe more

G

giuseppelt•8/31/23, 11:45 PM

but yesterday was working

C

Cyb3r-Jak3•8/31/23, 11:46 PM

I think there is an issue with wrangler 3.5.0 so you should stick to 3.4.X for now

U

Unsmart•8/31/23, 11:47 PM

If that doesnt fix it search the discord

__D1_BETA__DB

__D1_BETA__DB

__D1_BETA__DB

__D1_BETA__DB and you will see lots of convos about it might be able to find something to fix it there

G

giuseppelt•8/31/23, 11:56 PM

downgrade to wrangler 3.4.0 worked

G

giuseppelt•8/31/23, 11:56 PM

thanks

C

Cyb3r-Jak3•9/1/23, 12:03 AM

@giuseppelt is the code you’re hitting this with public? An issue should probably be made on the workers SDK repo

N

Nasr•9/1/23, 11:24 AM

are they any good migration or ORM work around for d1? thank you

NNasr are they any good migration or ORM work around for d1? thank you

M

Matt SilverlockOP•9/1/23, 11:59 AM

https://developers.cloudflare.com/d1/platform/community-projects/

Community projects · Cloudflare D1 docs

Members of the Cloudflare developer community and broader developer ecosystem have built and/or contributed tooling — including ORMs (Object …

D

Donnager•9/1/23, 4:58 PM

hello all, n00b Q:
Using nextjs-on-pages + cf-binding-proxy + d1 + lucia:

e: TypeError: (intermediate value) is not iterable
at Object.getSessionAndUser (webpack-internal:///(rsc)/./node_modules/.pnpm/@lucia-auth+adapter-sqlite@2.0.0_better-sqlite3@8.5.2_lucia@2.4.0/node_modules/@lucia-auth/adapter-sqlite/dist/drivers/d1.js:145:89)

the offending code:

const [{ results: sessionResults},{ results: userFromJoinResults }] 

= (await db.batch([                     getSessionStatement,          getUserFromJoinStatement
]));

const [{ results: sessionResults},{ results: userFromJoinResults }] 

= (await db.batch([                     getSessionStatement,          getUserFromJoinStatement
]));

const [{ results: sessionResults},{ results: userFromJoinResults }] 

= (await db.batch([                     getSessionStatement,          getUserFromJoinStatement
]));

const [{ results: sessionResults},{ results: userFromJoinResults }] 

= (await db.batch([                     getSessionStatement,          getUserFromJoinStatement
]));

i adjusted syntax:

                        const batchRes = (await db.batch([
                            getSessionStatement,
                            getUserFromJoinStatement
                        ]));
                        const sessionResults = batchRes[0].results
                        const userFromJoinResults = batchRes[1].results

                        const batchRes = (await db.batch([
                            getSessionStatement,
                            getUserFromJoinStatement
                        ]));
                        const sessionResults = batchRes[0].results
                        const userFromJoinResults = batchRes[1].results

                        const batchRes = (await db.batch([
                            getSessionStatement,
                            getUserFromJoinStatement
                        ]));
                        const sessionResults = batchRes[0].results
                        const userFromJoinResults = batchRes[1].results

                        const batchRes = (await db.batch([
                            getSessionStatement,
                            getUserFromJoinStatement
                        ]));
                        const sessionResults = batchRes[0].results
                        const userFromJoinResults = batchRes[1].results

now it passes, but i don't understand why, i was originally on node 16, but upgraded to 18 and still same error, if anyone has any thoughts super open to feedback, my first thought is something is wrong with versioning of JS or something since its just a syntax issue, but also not sure if its something i misconfigured for d1

DDonnager hello all, n00b Q: Using nextjs-on-pages + cf-binding-proxy + d1 + lucia: e: T...

J

James•9/1/23, 5:12 PM

Hello, thanks for reporting this. I've just pushed a new release for

cf-bindings-proxy

cf-bindings-proxy

cf-bindings-proxy

cf-bindings-proxy (v0.5.0) to fix this bug.

JJames Hello, thanks for reporting this. I've just pushed a new release for `cf-binding...

D

Donnager•9/1/23, 5:42 PM

oh awesome!! thank you for letting me know sir!

Original message was deleted

M

Matt SilverlockOP•9/1/23, 8:33 PM

No, but setting an automatic

expires_at

expires_at

expires_at

expires_at column and using that in your queries (and indexes) can get you there. You can do a cleanup with another trigger or a Cron Trigger Worker that runs periodically and separately cleans up

WHERE expires_at < now()

WHERE expires_at < now()

WHERE expires_at < now()

WHERE expires_at < now()

Original message was deleted

M

Matt SilverlockOP•9/1/23, 8:34 PM

FWIW, Postgres / MySQL don't do this without custom extensions, and the approach is the same. You could also use a view that elides "expired" rows and query that.

`json_each` - https://developers.cloudflare.com/d1/learning/querying-json/#supported-functions

Similar Threads