```Parse error near line 163: near "VALUES": syntax error INSERT INTO "keyedData" ("key", "data" V

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 ---^

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

not a line number but almost better

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

anyway now im having a bizare error

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

I have two identical .sql files

StronkOP•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...

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

that looks like the editor reported it, not sqlite

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

(works with sqlite3)

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

cuz it's syntax error.

StronkOP•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 ---^

vs
d1:

X [ERROR] near "(": syntax error

X [ERROR] near "(": syntax error

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

Parse error near line 135

Parse error near line 135

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

it's parse errorparse error which mean editor detected it.

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

what editor?

SStronk what editor?

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

terminal interactive?

StronkOP•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"

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

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

u said it, the bin

sqlite3

sqlite3

detected it, not the sqlite engine itself.

StronkOP•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)

StronkOP•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

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

nvm

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

so they arent identical

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

StronkOP•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 ...

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

i dont exactly understand what your saying

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

Are you using wrangler d1 execute?

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

yeah

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

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

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

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

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

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

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

StronkOP•8/16/23, 7:17 AM

that is good enough to find it

StronkOP•8/16/23, 7:17 AM

but its just like some closing paren might have an error somewhere near it lmao

StronkOP•8/16/23, 7:17 AM

like thanks that will totaly help me find it

StronkOP•8/16/23, 7:18 AM

also this code block was causing the errors I was seeing (that works in sqlite3 localy but not on d1 local or remote)

-- CREATE TRIGGER check_lineValuesAreValidIndexes BEFORE
-- INSERT ON lines FOR EACH ROW BEGIN
-- SELECT CASE
--         WHEN (
--             (
--                 SELECT lineManagerId
--                 FROM lineManagers
--                 WHERE lineManagerId = NEW.lineCreator
--             ) IS NULL
--         ) THEN RAISE(
--             ABORT,
--             'lineCreator not found in lineManagers table'
--         )
--     END;
-- END;

-- CREATE TRIGGER check_lineValuesAreValidIndexes BEFORE
-- INSERT ON lines FOR EACH ROW BEGIN
-- SELECT CASE
--         WHEN (
--             (
--                 SELECT lineManagerId
--                 FROM lineManagers
--                 WHERE lineManagerId = NEW.lineCreator
--             ) IS NULL
--         ) THEN RAISE(
--             ABORT,
--             'lineCreator not found in lineManagers table'
--         )
--     END;
-- END;

StronkOP•8/16/23, 7:18 AM

i dont understand why that would be a problem as its all comented out

StronkOP•8/16/23, 7:18 AM

lmao

StronkOP•8/16/23, 7:19 AM

I think this is acutaly a problem with d1

SStronk I think this is acutaly a problem with d1

Matt Silverlock•8/16/23, 2:41 PM

Please open an issue with a clear reproduction — e.g. a file that we can run, including the commands you run - so we can take a look: https://github.com/cloudflare/workers-sdk/issues/new?assignees=&labels=bug&projects=&template=bug-template.yaml&title=%F0%9F%90%9B+BUG%3A

CCyb3r-Jak3 If you share your account ID and database ID someone can probably take a look wh...

Matt Silverlock•8/16/23, 2:42 PM

We're taking a look into some of these cases to understand why some DBs got stuck overnight. If folks have a DB that is NOT responding to queries, reply with your account ID and database ID (these are OK to be shared publicly) to this message.

benjamin•8/16/23, 3:48 PM

It appears that triggers are supported (applied several to my tables) but wanted to confirm and see if there is any documentation or potential future considerations (lack of support). Thanks!

Bbenjamin It appears that triggers are supported (applied several to my tables) but wanted...

Matt Silverlock•8/16/23, 4:48 PM

No intent to remove support. We just haven’t documented them yet (note: this is for the new backend)

StronkOP•8/16/23, 5:48 PM

Are there docs for D1 further than just how the bindings work?

SStronk Are there docs for D1 further than just how the bindings work?

Matt Silverlock•8/16/23, 6:12 PM

What are you specifically after?

SStronk Are there docs for D1 further than just how the bindings work?

Matt Silverlock•8/16/23, 6:13 PM

Get started: https://developers.cloudflare.com/d1/get-started/
The client API: https://developers.cloudflare.com/d1/platform/client-api/
Indexes, JSON, local dev, debugging, time travel, etc, etc:https://developers.cloudflare.com/d1/learning/

Rabid•8/17/23, 3:15 AM

I am super excited about D1, do you envision it basically being a drop in replacement for something like RDS? I know there are drawbacks right now to max DB size and what not, but do you see this evolving to be as powerful as something like RDS or Aurora eventually?

Elliot Hesp•8/17/23, 3:47 AM

Just came across this blog post. Are procedures a thing or not? Don't see any reference to them in the docs

Elliot Hesp•8/17/23, 3:52 AM

Dang

having constant issues with prismas data proxy, would love to use d1 but without transaction support it seems like a no go

Elliot Hesp•8/17/23, 3:54 AM

Yeah that's our usecase unfortunately

```Parse error near line 163: near "VALUES": syntax error INSERT INTO "keyedData" ("key", "data" V

Similar Threads

Similar Threads

Similar Threads