If you share your account ID and database ID someone can probably take a look when they get a chance

B

benthecarman•8/16/23, 2:51 AM

seems to be back up, not too sure what happened

S

Stronk•8/16/23, 3:07 AM

why am I allowed to insert strings into int value collumns

S

Stronk•8/16/23, 3:21 AM

nvm its an sqlite thing

Ggeelen what's your DB id, I can have a look what happened

B

benthecarman•8/16/23, 3:46 AM

fba9bfa8-37e0-4c2f-a74c-4b466a2f4251

B

benthecarman•8/16/23, 3:46 AM

seems to be happening again too

B

benthecarman•8/16/23, 3:50 AM

and making requests to the database too

Ggeelen ok, i'm taking a look

B

benthecarman•8/16/23, 4:30 AM

lmk if any updates, still seems to be down

S

Stronk•8/16/23, 6:25 AM

why are errors from running a .sql file on d1 so damn vague, I need a line number

X [ERROR] near ")": syntax error

X [ERROR] near ")": syntax error

X [ERROR] near ")": syntax error

X [ERROR] near ")": syntax error

K

kian•8/16/23, 6:59 AM

I don't think SQLite even gives you a line number for syntax errors

C

chientrm.com•8/16/23, 7:00 AM

near

near

near

near

SStronk why are errors from running a .sql file on d1 so damn vague, I need a line numbe...

C

chientrm.com•8/16/23, 7:00 AM

can run 1 query at a time

S

Stronk•8/16/23, 7:00 AM

lmao

S

Stronk•8/16/23, 7:00 AM

sqlite does give line numbers

K

kian•8/16/23, 7:01 AM

sqlite3ErrorMsg(pParse, "near \"%T\": syntax error", &TOKEN);

sqlite3ErrorMsg(pParse, "near \"%T\": syntax error", &TOKEN);

sqlite3ErrorMsg(pParse, "near \"%T\": syntax error", &TOKEN);

sqlite3ErrorMsg(pParse, "near \"%T\": syntax error", &TOKEN);

K

kian•8/16/23, 7:01 AM

~~Feel free to indicate where that is in this line~~ Line numbers are dictated by https://github.com/sqlite/sqlite/blob/ff9ff548018bbe276dbd7bf5418af8bdfd659a24/src/shell.c.in#L11572-L11578

K

kian•8/16/23, 7:01 AM

Some errors? Sure, it does.

K

kian•8/16/23, 7:01 AM

But... that's far from all errors.

S

Stronk•8/16/23, 7:01 AM

Parse error near line 163: near "VALUES": syntax error
  INSERT INTO "keyedData" ("key", "data" VALUES ('expirationTimeForJWT', '216000
                           error here ---^

Parse error near line 163: near "VALUES": syntax error
  INSERT INTO "keyedData" ("key", "data" VALUES ('expirationTimeForJWT', '216000
                           error here ---^

Parse error near line 163: near "VALUES": syntax error
  INSERT INTO "keyedData" ("key", "data" VALUES ('expirationTimeForJWT', '216000
                           error here ---^

Parse error near line 163: near "VALUES": syntax error
  INSERT INTO "keyedData" ("key", "data" VALUES ('expirationTimeForJWT', '216000
                           error here ---^

S

Stronk•8/16/23, 7:01 AM

not a line number but almost better

S

Stronk•8/16/23, 7:01 AM

anyway now im having a bizare error

S

Stronk•8/16/23, 7:02 AM

I have two identical .sql files

S

Stronk•8/16/23, 7:02 AM

but one throws errors when running in d1 wrangler

SStronk ```Parse error near line 163: near "VALUES": syntax error INSERT INTO "keyedDa...

C

chientrm.com•8/16/23, 7:02 AM

that looks like the editor reported it, not sqlite

S

Stronk•8/16/23, 7:02 AM

(works with sqlite3)

C

chientrm.com•8/16/23, 7:02 AM

cuz it's syntax error.

S

Stronk•8/16/23, 7:05 AM

sqlite3:

Parse error near line 135: near "(": syntax error
  nnedOut IS dateTime(timeScannedOut))  PRIMARY KEY (lineNum, ticketNumber) );
                                      error here ---^

Parse error near line 135: near "(": syntax error
  nnedOut IS dateTime(timeScannedOut))  PRIMARY KEY (lineNum, ticketNumber) );
                                      error here ---^

Parse error near line 135: near "(": syntax error
  nnedOut IS dateTime(timeScannedOut))  PRIMARY KEY (lineNum, ticketNumber) );
                                      error here ---^

Parse error near line 135: near "(": syntax error
  nnedOut IS dateTime(timeScannedOut))  PRIMARY KEY (lineNum, ticketNumber) );
                                      error here ---^

vs
d1:

X [ERROR] near "(": syntax error

X [ERROR] near "(": syntax error

X [ERROR] near "(": syntax error

X [ERROR] near "(": syntax error

C

chientrm.com•8/16/23, 7:06 AM

Parse error near line 135

Parse error near line 135

Parse error near line 135

Parse error near line 135

C

chientrm.com•8/16/23, 7:06 AM

it's

parse error

parse error

parse error

parse error which mean editor detected it.

S

Stronk•8/16/23, 7:06 AM

what editor?

SStronk what editor?

C

chientrm.com•8/16/23, 7:06 AM

terminal interactive?

S

Stronk•8/16/23, 7:06 AM

that is the message from the command

sqlite3 Test.db ".read testdata.sql"

sqlite3 Test.db ".read testdata.sql"

sqlite3 Test.db ".read testdata.sql"

sqlite3 Test.db ".read testdata.sql"

SStronk that is the message from the command ```sqlite3 Test.db ".read testdata.sql"```

C

chientrm.com•8/16/23, 7:07 AM

u said it, the bin

sqlite3

sqlite3

sqlite3

sqlite3 detected it, not the sqlite engine itself.

S

Stronk•8/16/23, 7:07 AM

anyway my actual problem is the ghost in my computer that gives me diffrent results from two .sql files I run through d1 even though they are identical (I checked them in a bindary data viewer)

S

Stronk•8/16/23, 7:08 AM

one runs fine, the other gives me this error

X [ERROR] The supplied SQL string contains more than one statement

X [ERROR] The supplied SQL string contains more than one statement

X [ERROR] The supplied SQL string contains more than one statement

X [ERROR] The supplied SQL string contains more than one statement

S

Stronk•8/16/23, 7:11 AM

nvm

S

Stronk•8/16/23, 7:11 AM

so they arent identical

K

kian•8/16/23, 7:11 AM

At a glance line numbers are only if you pass in a file and D1 (iirc) splits up statements and doesn’t submit a file

S

Stronk•8/16/23, 7:11 AM

but the only diffrence is various comments

Kkian At a glance line numbers are only if you pass in a file and D1 (iirc) splits up ...

S

Stronk•8/16/23, 7:12 AM

i dont exactly understand what your saying

K

kian•8/16/23, 7:12 AM

Are you using wrangler d1 execute?

S

Stronk•8/16/23, 7:12 AM

yeah

K

kian•8/16/23, 7:13 AM

https://github.com/cloudflare/workers-sdk/blob/main/packages/wrangler/src/d1/execute.tsx#L289

GitHub

workers-sdk/packages/wrangler/src/d1/execute.tsx at main · cloudfla...

Home to Wrangler, the CLI for Cloudflare Workers® - cloudflare/workers-sdk

K

kian•8/16/23, 7:14 AM

It doesn’t see a file (like your .read example would), it sends the statements in its own batches - so there isn’t really any line number. I suspect it could give you a batch, but then it’d be hard to tell which statement in that batch was the issue

K

kian•8/16/23, 7:16 AM

Not saying it can’t be improved, just that this is how it is currently implemented

S

Stronk•8/16/23, 7:16 AM

ah

S

Stronk•8/16/23, 7:16 AM

well it could repeat the line that caused the error in full

If you share your account ID and database ID someone can probably take a look when they get a chance

Similar Threads

Similar Threads

Similar Threads