Will do 🙂

Iitsmatteomanf Will do 🙂

I

itsmatteomanfOP•6/3/23, 2:32 PM

Done, https://github.com/cloudflare/workerd/issues/729

GitHub

🐛 Bug Report — Runtime APIs: : D1 Does Not Allow `ALTER TABLE RENAM...

The Experimental Backend doesn't allow using ALTER TABLE RENAME COLUMN which should be supported in latest SQLite.

Iitsmatteomanf Done, https://github.com/cloudflare/workerd/issues/729

M

Matt Silverlock•6/3/23, 3:18 PM

d1-database

MMatt Silverlock https://discord.com/channels/595317990191398933/992060581832032316/1109973517182...

I

itsmatteomanfOP•6/3/23, 3:18 PM

Oh, sorry… I tried searching, but resulted in nothing NotLikeThis

I

itsmatteomanfOP•6/3/23, 3:19 PM

Discord search is so bad

Llokiwind Hello. I created a table. And this table will have three headers **key-time-va...

L

lokiwind•6/3/23, 3:36 PM

I need some help with this. MeowHeartCloudflare

Llokiwind I need some help with this. <:MeowHeartCloudflare:897193652089155645> 🤔

I

itsmatteomanfOP•6/3/23, 3:36 PM

In which sense "automatically" change?

L

lokiwind•6/3/23, 3:37 PM

I want a saved data to update itself after 30 seconds

I

itsmatteomanfOP•6/3/23, 3:38 PM

Oh yeah, then that's not possible.

I

itsmatteomanfOP•6/3/23, 3:38 PM

You need to do a query to update it.

I

itsmatteomanfOP•6/3/23, 3:38 PM

It's SQLite after all...

L

lokiwind•6/3/23, 3:39 PM

How can I make a query for this?
Can you give advice

L

lokiwind•6/3/23, 3:41 PM

The time of recording the data are all different from each other

L

lokiwind•6/3/23, 3:41 PM

When I send a request every 30 seconds this will not work some data will change earlier

Zzszszsz I don't understand the problem. And I don't understand why.

L

lokiwind•6/3/23, 3:43 PM

Are you talking to me?

Llokiwind After 30 seconds, the line will look like this. **TESTKEY123-00:00:00-1**

L

lokiwind•6/3/23, 3:44 PM

I explained in detail here

L

lokiwind•6/3/23, 3:47 PM

I will explain in a simple way

L

lokiwind•6/3/23, 3:48 PM

Let's say I saved data with a value of 1 in a table with D1

L

lokiwind•6/3/23, 3:49 PM

I want this 1 value to be updated to 0 after 30 seconds

L

lokiwind•6/3/23, 3:50 PM

Required for my project

L

lokiwind•6/3/23, 3:50 PM

To set a key time

L

lokiwind•6/3/23, 3:51 PM

I just want to replace the expired value, that's all.

L

lokiwind•6/3/23, 3:53 PM

Hmm

L

lokiwind•6/3/23, 3:54 PM

Thank you, I will try

Zzszszsz hmm is it really what you want ?

L

lokiwind•6/3/23, 4:06 PM

If he can do what I want him to do.

Y

yeehow•6/3/23, 5:16 PM

Running into this error (using Drizzle ORM)

Error: D1_ERROR
    at D1Database._send (index.js:2874:13)
    at async D1PreparedStatement.raw (index.js:2945:7)
    at async PreparedQuery2.all (index.js:2367:18)
    at async index.js:2761:18
    at async Object.handle [as fetch] (index.js:21:30) {
  stack: Error: D1_ERROR
    at D1Database._send (index.js:…t async Object.handle [as fetch] (index.js:21:30),
  message: D1_ERROR,
  cause: Error: Error: too many arguments on function json_array
    at D1Database._send (index.js:2875:16)
…
}

Error: D1_ERROR
    at D1Database._send (index.js:2874:13)
    at async D1PreparedStatement.raw (index.js:2945:7)
    at async PreparedQuery2.all (index.js:2367:18)
    at async index.js:2761:18
    at async Object.handle [as fetch] (index.js:21:30) {
  stack: Error: D1_ERROR
    at D1Database._send (index.js:…t async Object.handle [as fetch] (index.js:21:30),
  message: D1_ERROR,
  cause: Error: Error: too many arguments on function json_array
    at D1Database._send (index.js:2875:16)
…
}

Error: D1_ERROR
    at D1Database._send (index.js:2874:13)
    at async D1PreparedStatement.raw (index.js:2945:7)
    at async PreparedQuery2.all (index.js:2367:18)
    at async index.js:2761:18
    at async Object.handle [as fetch] (index.js:21:30) {
  stack: Error: D1_ERROR
    at D1Database._send (index.js:…t async Object.handle [as fetch] (index.js:21:30),
  message: D1_ERROR,
  cause: Error: Error: too many arguments on function json_array
    at D1Database._send (index.js:2875:16)
…
}

Error: D1_ERROR
    at D1Database._send (index.js:2874:13)
    at async D1PreparedStatement.raw (index.js:2945:7)
    at async PreparedQuery2.all (index.js:2367:18)
    at async index.js:2761:18
    at async Object.handle [as fetch] (index.js:21:30) {
  stack: Error: D1_ERROR
    at D1Database._send (index.js:…t async Object.handle [as fetch] (index.js:21:30),
  message: D1_ERROR,
  cause: Error: Error: too many arguments on function json_array
    at D1Database._send (index.js:2875:16)
…
}

Works fine when running locally, but gives this error when running remotely or deployed.

Leads me to believe D1 has a lower

json_array()

json_array()

json_array()

json_array() argument limit than standard SQLite?
From my testing it seams to only work with up to 8 arguments.

Just a theory. Don't really know what I'm doing

Yyeehow Running into this error (using Drizzle ORM) ``` Error: D1_ERROR at D1Databas...

M

Matt Silverlock•6/3/23, 5:21 PM

https://developers.cloudflare.com/d1/platform/limits/

(Function arguments are being bumped to 32 in the next week)

Limits · Cloudflare D1 docs

Many of these limits will increase during D1’s public alpha. Join the #d1-open-alpha channel in the Cloudflare Developer Discord to keep up to date …

H

hanpolo•6/3/23, 6:28 PM

I have upgraded to wrangler 3.0.1 and my previously persisted database no longer works. The error I get is that tables I created in the persisted database are not present. I ran my migrations again and noticed that two databases were created under .wrangler/state/v3/d1/<some random string> & .wrangler/state/v3/d1/my_d1 with the <some random string> database having the tables and my_d1 being empty. But even after this, when I tried accessing the database I got the same error. I did notice a line when wrangler initialized : "my_d1: local-my_d1 (my_d1)." Any ideas on what I have to do to get back to my database?

MMatt Silverlock https://developers.cloudflare.com/d1/platform/limits/ (Function arguments are ...

Y

yeehow•6/3/23, 6:35 PM

Someone how missed this... Great to hear thank you!

Hhanpolo I have upgraded to wrangler 3.0.1 and my previously persisted database no longer...

M

Matt Silverlock•6/3/23, 7:48 PM

Wrangler 3 changed the location and format of persisted data - if you search this channel you’ll find a couple of others talking about it. Do you need the local data for some reason?

H

hanpolo•6/3/23, 8:17 PM

Nope, don't need the old data .. just need to be able to access local data ..

H

hanpolo•6/3/23, 8:17 PM

I'll search some more

H

hanpolo•6/3/23, 8:23 PM

My problem is not getting hold of old data. I upgraded to wrangler 3, ran my migrations again, a database was created in the .wrangler/state/v3/d1/<UUID> location, and still can't get hold of any of the tables created by migration scripts

H

hanpolo•6/3/23, 8:27 PM

I just ran a test and created a table from my main "functions" code with local binding. It created the table in .wrangler/state/v3/d1/my_d1 instead of d1/<UUID>. Am I missing some setting? This is cumbersome because now my migrations are creating tables in d1/<UUID> but my functions scripts are looking at d1/my_d1

H

hanpolo•6/3/23, 8:29 PM

my wrangler command is:

npx wrangler pages dev --d1=my_d1

npx wrangler pages dev --d1=my_d1

npx wrangler pages dev --d1=my_d1

npx wrangler pages dev --d1=my_d1

H

hanpolo•6/3/23, 8:30 PM

do I need to use --persist-to?

H

hanpolo•6/3/23, 8:33 PM

my migration command is

npx wrangler d1 migrations apply -e staging my_d1 --local

npx wrangler d1 migrations apply -e staging my_d1 --local

npx wrangler d1 migrations apply -e staging my_d1 --local

npx wrangler d1 migrations apply -e staging my_d1 --local

H

hanpolo•6/3/23, 8:35 PM

And my wrangler.toml has:

[env.staging]
d1_databases = [
  { binding = "my_d1", database_name = "my_d1_preview", database_id = <UUID> }
]

[env.staging]
d1_databases = [
  { binding = "my_d1", database_name = "my_d1_preview", database_id = <UUID> }
]

[env.staging]
d1_databases = [
  { binding = "my_d1", database_name = "my_d1_preview", database_id = <UUID> }
]

[env.staging]
d1_databases = [
  { binding = "my_d1", database_name = "my_d1_preview", database_id = <UUID> }
]

H

hanpolo•6/3/23, 9:31 PM

Ok .. in summary we have a problem:

--persist-to will not work since it moves the entire persistence directory
the migrate tool goes off wrangler.toml and hence puts migrations to .wrangler/state/v3/d1/<UUID>
but `npx wrangler pages dev --d1=<BINDING> reads the database off of .wrangler/state/v3/d1/<BINDING>.

The only solution I see for myself at this point is to follow a manual procedure on each database migration:

copy database from d1/<BINDING> to d1/<UUID>
run the migration
copy migrated database from d1/<UUID> back to d1/<BINDING>

I wonder if this is intentional or a bug?

Hhanpolo Ok .. in summary we have a problem: 1. --persist-to will not work since it move...

M

Matt Silverlock•6/3/23, 9:43 PM

wrangler v3 moved all of the local persistence to a new directory (not specific to D1). You have to assume a clean slate - e.g. apply all migrations again.

Similar Threads