character 245

UUnsmart character 245

V

Vikash•7/6/24, 4:17 AM

Got it, thanks.

V

Vikash•7/6/24, 10:10 AM

New error:

{"D1_RESET_DO":true}

{"D1_RESET_DO":true}

{"D1_RESET_DO":true}

{"D1_RESET_DO":true} Any idea what is this?

O

Old Man Maker•7/6/24, 2:16 PM

it is seriously rediculous that we can name a table with a - dash in it within the CF dashboard, but doing a PRAGMA table_info fails. I think I mentioned this several months ago.

C

Chinoman10•7/6/24, 11:54 PM

Error: D1_TYPE_ERROR: Type 'object' not supported for value '123string,134,123string,0,0.17,comercial@

Error: D1_TYPE_ERROR: Type 'object' not supported for value '123string,134,123string,0,0.17,comercial@

Error: D1_TYPE_ERROR: Type 'object' not supported for value '123string,134,123string,0,0.17,comercial@

Error: D1_TYPE_ERROR: Type 'object' not supported for value '123string,134,123string,0,0.17,comercial@ (...)

Any ideas? I already tried searching around and reading all the docs back and forth.

C

Chinoman10•7/7/24, 12:07 AM

... found it :facepalm:

C

Chinoman10•7/7/24, 12:08 AM

turns out building wrappers for nice abstraction is only good if you test it our extensively...

C

Chinoman10•7/7/24, 12:08 AM

I was missing the spread operator on the params that I was passing.

C

Chinoman10•7/7/24, 12:41 AM

D

dog1283•7/7/24, 6:58 PM

Hi All, I am facing an issue using D1 locally. The issue is my worker cannot see any of the DB objects I have created.

First, I setup my DB with some DDL:

wrangler d1 execute appdb-dev --local --file=./1.sql

wrangler d1 execute appdb-dev --local --file=./1.sql

wrangler d1 execute appdb-dev --local --file=./1.sql

wrangler d1 execute appdb-dev --local --file=./1.sql

Then I can query the DB:

wrangler d1 execute appdb-dev --local --command="SELECT * FROM User"

wrangler d1 execute appdb-dev --local --command="SELECT * FROM User"

wrangler d1 execute appdb-dev --local --command="SELECT * FROM User"

wrangler d1 execute appdb-dev --local --command="SELECT * FROM User" // works

However, when I try to access my local d1 instance in the worker, it can't find any tables. It is obviously looking at some other local instance, but I can't find any way to list the local instances, or don't know the commands to understand whether I am looking at the right one.

Any ideas? Wrangler.toml below:

name = "app-services"
compatibility_date = "2023-12-01"
route = "api.myapp.app/*"
compatibility_flags = ["nodejs_compat"]

[vars]
LOG_LEVEL="debug"
TEST_MODE="TRUE"
kv_namespaces = [
    { binding = "MYAPP_TOKENS", preview_id = "###", id = "###" },
]

[[d1_databases]]
binding = "DB"
database_name = "appdb-dev"
database_id = "###"
preview_database_id = "appdb-dev"

[env.dev]
route = "dev-api.myapp.app/*"

name = "app-services"
compatibility_date = "2023-12-01"
route = "api.myapp.app/*"
compatibility_flags = ["nodejs_compat"]

[vars]
LOG_LEVEL="debug"
TEST_MODE="TRUE"
kv_namespaces = [
    { binding = "MYAPP_TOKENS", preview_id = "###", id = "###" },
]

[[d1_databases]]
binding = "DB"
database_name = "appdb-dev"
database_id = "###"
preview_database_id = "appdb-dev"

[env.dev]
route = "dev-api.myapp.app/*"

name = "app-services"
compatibility_date = "2023-12-01"
route = "api.myapp.app/*"
compatibility_flags = ["nodejs_compat"]

[vars]
LOG_LEVEL="debug"
TEST_MODE="TRUE"
kv_namespaces = [
    { binding = "MYAPP_TOKENS", preview_id = "###", id = "###" },
]

[[d1_databases]]
binding = "DB"
database_name = "appdb-dev"
database_id = "###"
preview_database_id = "appdb-dev"

[env.dev]
route = "dev-api.myapp.app/*"

name = "app-services"
compatibility_date = "2023-12-01"
route = "api.myapp.app/*"
compatibility_flags = ["nodejs_compat"]

[vars]
LOG_LEVEL="debug"
TEST_MODE="TRUE"
kv_namespaces = [
    { binding = "MYAPP_TOKENS", preview_id = "###", id = "###" },
]

[[d1_databases]]
binding = "DB"
database_name = "appdb-dev"
database_id = "###"
preview_database_id = "appdb-dev"

[env.dev]
route = "dev-api.myapp.app/*"

VVikash New error: `{"D1_RESET_DO":true}` Any idea what is this?

S

slagathor•7/8/24, 3:41 AM

I'm running into this as well. Have you been able to resolve it?

Sslagathor I'm running into this as well. Have you been able to resolve it?

V

Vikash•7/8/24, 3:57 AM

No, the import on D1 is super buggy. I was unable to import a small DB of 1gb as well.

VVikash No, the import on D1 is super buggy. I was unable to import a small DB of 1gb as...

S

slagathor•7/8/24, 5:08 AM

Hmm...interesting. This is the first time I've ran into this issue

S

slagathor•7/8/24, 5:08 AM

wonder if an update was pushed

OOld Man Maker it is seriously rediculous that we can name a table with a - dash in it within t...

M

Max (@rozenmd)•7/8/24, 11:15 AM

?

SSteffTek thanks, looks like my databases are running in WNAM... great for european users ...

M

Max (@rozenmd)•7/8/24, 11:34 AM

Looks like I overlooked adding the location hint into our OpenAPI spec, which means it isn't available for terraform. Will fix.

MMax (@rozenmd)Looks like I overlooked adding the location hint into our OpenAPI spec, which me...

S

SteffTek•7/8/24, 11:35 AM

that would be great <3

Original message was deleted

L

luna•7/8/24, 11:39 AM

i just hit something similar. i cant delete my tables at all in the dashboard

i get the following error when attempting to delete the table.

FOREIGN KEY constraint failed (Code: 7500)

FOREIGN KEY constraint failed (Code: 7500)

FOREIGN KEY constraint failed (Code: 7500)

FOREIGN KEY constraint failed (Code: 7500)

Lluna i just hit something similar. i cant delete my tables at all in the dashboard 😅...

M

Max (@rozenmd)•7/8/24, 11:46 AM

Are you able to provide a sample schema that reproduces the issue? last time we tried, we couldn't repro it d1-database

MMax (@rozenmd)Are you able to provide a sample schema that reproduces the issue? last time we ...

L

luna•7/8/24, 11:50 AM

yes and i worked out the issue. i’ll upload a code example in a bit.

MMax (@rozenmd)Are you able to provide a sample schema that reproduces the issue? last time we ...

L

luna•7/8/24, 1:33 PM

CREATE TABLE
    user (
        id TEXT NOT NULL PRIMARY KEY,
        username TEXT NOT NULL,
        email TEXT NOT NULL,
        password_hash TEXT NOT NULL,
        created_at INTEGER NOT NULL,
        updated_at INTEGER NOT NULL
    );

CREATE TABLE
    session (
        id TEXT NOT NULL PRIMARY KEY,
        expires_at INTEGER NOT NULL,
        user_id TEXT NOT NULL,
        FOREIGN KEY (user_id) REFERENCES user (id)
    );

CREATE TABLE
    user (
        id TEXT NOT NULL PRIMARY KEY,
        username TEXT NOT NULL,
        email TEXT NOT NULL,
        password_hash TEXT NOT NULL,
        created_at INTEGER NOT NULL,
        updated_at INTEGER NOT NULL
    );

CREATE TABLE
    session (
        id TEXT NOT NULL PRIMARY KEY,
        expires_at INTEGER NOT NULL,
        user_id TEXT NOT NULL,
        FOREIGN KEY (user_id) REFERENCES user (id)
    );

CREATE TABLE
    user (
        id TEXT NOT NULL PRIMARY KEY,
        username TEXT NOT NULL,
        email TEXT NOT NULL,
        password_hash TEXT NOT NULL,
        created_at INTEGER NOT NULL,
        updated_at INTEGER NOT NULL
    );

CREATE TABLE
    session (
        id TEXT NOT NULL PRIMARY KEY,
        expires_at INTEGER NOT NULL,
        user_id TEXT NOT NULL,
        FOREIGN KEY (user_id) REFERENCES user (id)
    );

CREATE TABLE
    user (
        id TEXT NOT NULL PRIMARY KEY,
        username TEXT NOT NULL,
        email TEXT NOT NULL,
        password_hash TEXT NOT NULL,
        created_at INTEGER NOT NULL,
        updated_at INTEGER NOT NULL
    );

CREATE TABLE
    session (
        id TEXT NOT NULL PRIMARY KEY,
        expires_at INTEGER NOT NULL,
        user_id TEXT NOT NULL,
        FOREIGN KEY (user_id) REFERENCES user (id)
    );

i used the above schema and created users + sessions in my app. i then tried deleting both tables which wouldnt work. i had to delete the sessions table first and then the users.
would be nice if the error at least said which table caused the issue.

Lluna ```sql CREATE TABLE user ( id TEXT NOT NULL PRIMARY KEY, use...

S

SteffTek•7/8/24, 1:39 PM

sounds like regular sqlite

S

SteffTek•7/8/24, 1:40 PM

if you are using raw sql and not an ORM (like a mad man) you can start a transaction and set the foreign key pragma to OFF, then delete your stuff, and then turn the pragma back on

SSteffTek if you are using raw sql and not an ORM (like a mad man) you can start a transac...

L

luna•7/8/24, 1:49 PM

you cant do that with the dashboard and again "would be nice if the error at least said which table caused the issue."

S

SteffTek•7/8/24, 1:49 PM

Technically you can

L

luna•7/8/24, 1:49 PM

okay but im saying this is an issue. that response doesnt really help me.

S

SteffTek•7/8/24, 1:50 PM

Yeah like I said it's an sqlite problem not cloudflare

L

luna•7/8/24, 1:50 PM

okay..

SSteffTek Yeah like I said it's an sqlite problem not cloudflare

L

luna•7/8/24, 1:51 PM

a bit of advice. this isnt helpful at all.

S

SteffTek•7/8/24, 1:55 PM

Yeah I'm not support staff so tbh I don't really care if you find my advice helpful. I just tried to tell you cloudflare cannot really do much here

L

luna•7/8/24, 1:55 PM

incorrect. they can fix the error

next time just dont comment if you have nothing to add.

S

SteffTek•7/8/24, 2:01 PM

:lul:

FFinn 🔜 39C3 no i have to give stefftek a point here, you are referencing a user in a session...

L

luna•7/8/24, 2:09 PM

no it is not. this is a bug in the ui. the ui should be surfacing the full error which includes the table name.

im not posting here asking for help. i was asked by someone that works at cloudflare to reply. i really wish people would stop trying to but into things.

FFinn 🔜 39C3 (as far as i understand the problem at hand)

L

luna•7/8/24, 2:10 PM

no one asked you to. d1-database

S

SteffTek•7/8/24, 2:11 PM

It isn't even an error , it's by design you can't delete a referenced table entry

S

SteffTek•7/8/24, 2:11 PM

Lol

L

luna•7/8/24, 2:13 PM

... i didnt ask for help.

L

luna•7/8/24, 2:13 PM

please read before commenting it really helps.

K

kian•7/8/24, 2:14 PM

This isn't a place to discuss the merits of a given piece of feedback, please stop. The team are always interested in how to improve error messaging, like we've done before for syntax errors.

L

luna•7/8/24, 2:15 PM

exactly my point...

K

kian•7/8/24, 2:15 PM

Some SQLite errors are only enriched with information available in a shell (like when you run

sqlite3

sqlite3

sqlite3

sqlite3 locally) and the actual 'library' itself used by embedders doesn't show that.

L

luna•7/8/24, 2:15 PM

as a user this makes things harder. cloudflare tends to fix those types of issues. hence me posting about it.

L

luna•7/8/24, 2:16 PM

seems either it should detect this and delete them in the right order or at least tell me which table in the selection i picked that caused it.

K

kian•7/8/24, 2:16 PM

Yup, and we've done it before: https://github.com/cloudflare/workerd/pull/1392

K

kian•7/8/24, 2:17 PM

I have no idea if this particular error/scenario can be improved (technically), but the team can log it as a feature request/improvement nonetheless.

L

luna•7/8/24, 2:18 PM

plus at least if someone searches for that same error theyll hit this chat and hopefully realise the issue.

MMax (@rozenmd)?

O

Old Man Maker•7/8/24, 3:51 PM

Might be a Terminal or PowerShell issue? Had to rename the table to get info

Lluna ```sql CREATE TABLE user ( id TEXT NOT NULL PRIMARY KEY, use...

M

Mayuresh Choudhary•7/9/24, 3:38 AM

It's because you've added foreign key constraints.

In SQL it's a basic thing, you need to delete all the dependent tables (tables which has foreign keys) and then you need to delete the independent table.

In your case session is the dependent table and user is the independent table.
So deleting user table and then session table would result into an error.

Ik sometimes error messages don't make sense but yeah this is the reason you got the error

Similar Threads

Similar Threads

Similar Threads