It's nice that we can now quickly edit our tables in the dashboard, however (at least yesterday when

N

NoelOP•3/14/23, 9:03 AM

so i think it would be good to have an option to select the encoding of the data

N

NoelOP•3/14/23, 9:04 AM

Like base64, base32, hex, etc or as-is (no encoding)

NNoel It's nice that we can now quickly edit our tables in the dashboard, however (at ...

M

Max (@rozenmd)•3/14/23, 10:16 AM

cheers for the heads up - i just added text/integer support to start with, will add a ticket for binary data

C

charl.dev•3/14/23, 11:50 AM

rozenmd, walshy erisa - thank you, 2715870 sorted and im unblocked

C

charl.dev•3/14/23, 11:54 AM

its regarding not being able to execute/create pages d1 with wrangler admin on ent

Cc becker A function (running in dev) is trying to use the db I created in the dashboard a...

M

Matt Silverlock•3/15/23, 12:52 AM

Are you using Pages? https://developers.cloudflare.com/pages/platform/functions/bindings/#interact-with-your-d1-databases-locally

Bindings · Cloudflare Pages docs

A binding enables your Pages Functions to interact with resources on the Cloudflare developer platform. Use bindings to integrate your Pages Functions …

MMatt Silverlock Are you using Pages? https://developers.cloudflare.com/pages/platform/functions/...

M

Matt Silverlock•3/15/23, 12:53 AM

Also:

By default, data in local development is not persisted. This means if you write a value into KV, for example, the next time you start local dev, it will no longer exist. Enable persistence with the --persist flag.

Cc becker interesting, this works: `wrangler d1 execute timely-tasker-dev --command "SELEC...

M

Matt Silverlock•3/15/23, 1:49 AM

I was just going to ask if you could query the table directly

M

Matt Silverlock•3/15/23, 1:50 AM

Can you confirm you also ran the migrations locally? I suspect your live DB is correct, and your local DB is not, and thus returns that error with

--local

--local

M

Matt Silverlock•3/15/23, 1:51 AM

--local

--local

means just that: local only. e.g. for local dev/CI/etc.

M

Matt Silverlock•3/15/23, 2:11 AM

When you call

wrangler pages dev

wrangler pages dev

are you passing

—d1=DB

—d1=DB

—d1=DB

—d1=DB as the docs direct? I haven’t seen you post a full command invocation and am wondering…

Jjschlesser I have a working next-auth / authjs d1 database adapter passing the next-auth un...

M

Max (@rozenmd)•3/15/23, 9:41 AM

if its in their repo, it should be fine

M

Mozzy•3/15/23, 9:19 PM

I'm at a loss as to why this doesn't work:

DROP TABLE IF EXISTS attempts;
CREATE TABLE attempts (pathname TEXT NOT NULL, correct_answer TEXT NOT NULL, user_answer TEXT);

DROP TABLE IF EXISTS attempts;
CREATE TABLE attempts (pathname TEXT NOT NULL, correct_answer TEXT NOT NULL, user_answer TEXT);

DROP TABLE IF EXISTS attempts;
CREATE TABLE attempts (pathname TEXT NOT NULL, correct_answer TEXT NOT NULL, user_answer TEXT);

DROP TABLE IF EXISTS attempts;
CREATE TABLE attempts (pathname TEXT NOT NULL, correct_answer TEXT NOT NULL, user_answer TEXT);

await DB.prepare("INSERT INTO attempts (pathname, correct_answer, user_answer) VALUES (?1, ?2, ?3)").bind(route.pathname, route.correctAnswer, userAnswer).run();
// All 3 variables are strings

await DB.prepare("INSERT INTO attempts (pathname, correct_answer, user_answer) VALUES (?1, ?2, ?3)").bind(route.pathname, route.correctAnswer, userAnswer).run();
// All 3 variables are strings

await DB.prepare("INSERT INTO attempts (pathname, correct_answer, user_answer) VALUES (?1, ?2, ?3)").bind(route.pathname, route.correctAnswer, userAnswer).run();
// All 3 variables are strings

await DB.prepare("INSERT INTO attempts (pathname, correct_answer, user_answer) VALUES (?1, ?2, ?3)").bind(route.pathname, route.correctAnswer, userAnswer).run();
// All 3 variables are strings

No errors running the JS.

Running

wrangler d1 execute DBNAME --command "SELECT * FROM attempts"

wrangler d1 execute DBNAME --command "SELECT * FROM attempts"

wrangler d1 execute DBNAME --command "SELECT * FROM attempts"

wrangler d1 execute DBNAME --command "SELECT * FROM attempts" results in:

Mapping SQL input into an array of statements
🌀 Parsing 1 statements
🌀 Executing on DBNAME (DBID):
🚣 Executed 1 command in 4.764229000080377ms
value of stdout.lastframe() is undefined

Mapping SQL input into an array of statements
🌀 Parsing 1 statements
🌀 Executing on DBNAME (DBID):
🚣 Executed 1 command in 4.764229000080377ms
value of stdout.lastframe() is undefined

Mapping SQL input into an array of statements
🌀 Parsing 1 statements
🌀 Executing on DBNAME (DBID):
🚣 Executed 1 command in 4.764229000080377ms
value of stdout.lastframe() is undefined

Mapping SQL input into an array of statements
🌀 Parsing 1 statements
🌀 Executing on DBNAME (DBID):
🚣 Executed 1 command in 4.764229000080377ms
value of stdout.lastframe() is undefined

Dashboard also returns nothing

wrangler -v:

wrangler 2.12.3

wrangler 2.12.3

wrangler 2.12.3

wrangler 2.12.3

M

Mozzy•3/15/23, 9:36 PM

Solved: was missing an await earlier in the code, causing the worker to return before completing the d1 task BlobDead

Original message was deleted

M

Mozzy•3/15/23, 9:42 PM

Seems like it

M

Mozzy•3/15/23, 9:45 PM

Yeah, will do tomorrow

B

bennycondon•3/15/23, 11:05 PM

I'm running the command:

wrangler d1 execute DB --file=./migrations/1673910000_init.sql --local --persist-to=./.wrangler

wrangler d1 execute DB --file=./migrations/1673910000_init.sql --local --persist-to=./.wrangler

wrangler d1 execute DB --file=./migrations/1673910000_init.sql --local --persist-to=./.wrangler

wrangler d1 execute DB --file=./migrations/1673910000_init.sql --local --persist-to=./.wrangler

If I don't include a wrangler.toml file with the name/binding for 'DB', I receive the error:

ERROR: Can't find a DB with name/binding 'DB' in local config. Check info in wrangler.toml...

ERROR: Can't find a DB with name/binding 'DB' in local config. Check info in wrangler.toml...

ERROR: Can't find a DB with name/binding 'DB' in local config. Check info in wrangler.toml...

ERROR: Can't find a DB with name/binding 'DB' in local config. Check info in wrangler.toml...

Is it possible to not include a wrangler.toml file, and instead pass the d1 binding directly in the command? For example, we do this with:

wrangler pages dev ./public --d1=DB --local --persist-to=./.wrangler

wrangler pages dev ./public --d1=DB --local --persist-to=./.wrangler

wrangler pages dev ./public --d1=DB --local --persist-to=./.wrangler

wrangler pages dev ./public --d1=DB --local --persist-to=./.wrangler

B

bennycondon•3/15/23, 11:07 PM

I'm on wrangler version 2.12.0

B

bennycondon•3/15/23, 11:08 PM

I'll update to 2.12.3 and see if that fixes it

B

bennycondon•3/15/23, 11:12 PM

Still getting the same error after updating

Original message was deleted

M

Max (@rozenmd)•3/16/23, 7:14 AM

D1 doesn't have extensions or a way to inject your own logic with a Worker yet, so if native SQLite has it turned on by default, we do too

Original message was deleted

M

Max (@rozenmd)•3/16/23, 10:11 AM

There's a few: https://developers.cloudflare.com/workers/learning/integrations/databases/

MMozzy Yeah, will do tomorrow

M

Mozzy•3/16/23, 6:33 PM

https://github.com/cloudflare/workers-sdk/issues/2907

M

meyer•3/17/23, 7:54 PM

big fan of workers-qb

It's nice that we can now quickly edit our tables in the dashboard, however (at least yesterday when

Similar Threads