what I'm wondering: why not use the same defaults for the local sqlite? if it blows when testing loc

Kkika so, until the PR is merged there's no workaround for me to use CHECK in ALTER TA...

M

Matt Silverlock•8/15/23, 8:05 PM

Unfortunately not.

Kkika what I'm wondering: why not use the same defaults for the local sqlite? if it bl...

M

Matt Silverlock•8/15/23, 8:05 PM

We should make these work the same. That's on us.

K

kikaOP•8/15/23, 8:07 PM

ok, thanks, no biggie, thanks for jumping on it so promptly. i can live with just a TEXT field without CHECKs

Ggeelen You can create a table with a CHECK constraint, you just can't add a CHECK const...

K

kikaOP•8/15/23, 11:12 PM

yeah, i figured, thanks!

Original message was deleted

S

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

any ideas for this issue?

B

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

is d1 down atm, we can't seem to get our database to load

Bbenthecarman is d1 down atm, we can't seem to get our database to load

C

Cyb3r-Jak3•8/16/23, 2:26 AM

Define not able to load. Mine are working fine

B

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

only options request load, cant view the table in dashboard

B

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

Bbenthecarman Click to see attachment

C

Cyb3r-Jak3•8/16/23, 2:32 AM

Do you see any console logs or request errors when attempted to view the table from the dash console

B

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

it wont load in the UI anymore now

C

Cyb3r-Jak3•8/16/23, 2:34 AM

Look in dev tools

B

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

there is a get database call failing with a 500 error

C

Cyb3r-Jak3•8/16/23, 2:36 AM

What is the error in the response

B

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

there wasn't anything

B

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

I refreshed and now getting 504s

C

Cyb3r-Jak3•8/16/23, 2:39 AM

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

what I'm wondering: why not use the same defaults for the local sqlite? if it blows when testing loc

Similar Threads