Hello! Is it an expected behavior for an UPDATE query to always take 1 rows_read?

BBeyondo Hello! Is it an expected behavior for an UPDATE query to always take 1 rows_read...

M

Is it just an UPDATE, or perhaps an

UPDATE ... RETURNING *

UPDATE ... RETURNING *

UPDATE ... RETURNING *

UPDATE ... RETURNING *?

M

Mongy•2/28/24, 3:45 PM

Anyone here have made API calls to a D1 instance to query the db?

The error im receiving:

The request is malformed: failed to decode id

The request is malformed: failed to decode id

The request is malformed: failed to decode id

The request is malformed: failed to decode id

url:

https://api.cloudflare.com/client/v4/accounts/{account_id}/d1/database/{db_id}/query

https://api.cloudflare.com/client/v4/accounts/{account_id}/d1/database/{db_id}/query

https://api.cloudflare.com/client/v4/accounts/{account_id}/d1/database/{db_id}/query

https://api.cloudflare.com/client/v4/accounts/{account_id}/d1/database/{db_id}/query

const insertStatement = `INSERT INTO table (column1, column2) VALUES ('value1', 'value2');`;

const insertStatement = `INSERT INTO table (column1, column2) VALUES ('value1', 'value2');`;

const insertStatement = `INSERT INTO table (column1, column2) VALUES ('value1', 'value2');`;

const insertStatement = `INSERT INTO table (column1, column2) VALUES ('value1', 'value2');`;

const options = {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      Authorization: 'Bearer {api_token}'
    },
    body: `{"sql": ${insertStatement}`
  }

const options = {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      Authorization: 'Bearer {api_token}'
    },
    body: `{"sql": ${insertStatement}`
  }

const options = {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      Authorization: 'Bearer {api_token}'
    },
    body: `{"sql": ${insertStatement}`
  }

const options = {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      Authorization: 'Bearer {api_token}'
    },
    body: `{"sql": ${insertStatement}`
  }

I'm not exactly where to go from here unfortunately. Any assistance would be greatly appreciated.

K

kian•2/28/24, 3:46 PM

Are you sure

db_id

db_id

db_id

db_id is right?

K

kian•2/28/24, 3:46 PM

You're also missing a closing bracket in your

body

body

from the looks of it

M

Mongy•2/28/24, 3:46 PM

copied straight from the d1 instance

K

kian•2/28/24, 3:47 PM

the

Authorization

Authorization

Authorization

Authorization header also doesn't seem to be actually interpolating the

api_token

api_token

api_token

api_token variable

M

Mongy•2/28/24, 3:48 PM

ive tried using

X-Auth-Key

X-Auth-Key

X-Auth-Key

X-Auth-Key but i get an error that it doesn't exist in the request

Kkian You're also missing a closing bracket in your `body` from the looks of it

M

Mongy•2/28/24, 3:48 PM

that's embarresing. Added the bracket but the error still persists

K

kian•2/28/24, 3:48 PM

It's probably an issue with the URL path or the API token

K

kian•2/28/24, 3:49 PM

What did you put in for

account_id

account_id

and

db_id

db_id

db_id

db_id? They're not sensitive.

M

Mongy•2/28/24, 3:49 PM

Account id:

4f6d1970bc967b2c2a90b643bbb5ac94

4f6d1970bc967b2c2a90b643bbb5ac94

4f6d1970bc967b2c2a90b643bbb5ac94

4f6d1970bc967b2c2a90b643bbb5ac94
db id:

0e35121-f3cc-4e24-b5c1-4d758860a69d

0e35121-f3cc-4e24-b5c1-4d758860a69d

0e35121-f3cc-4e24-b5c1-4d758860a69d

0e35121-f3cc-4e24-b5c1-4d758860a69d

M

Mongy•2/28/24, 3:50 PM

permissions for api token has read and write for D1

K

kian•2/28/24, 3:50 PM

Does the URL look correct if you

console.log

console.log

it?

M

Mongy•2/28/24, 3:52 PM

looks good

https://api.cloudflare.com/client/v4/accounts/4f6d1970bc967b2c2a90b643bbb5ac94/d1/database/0e35121-f3cc-4e24-b5c1-4d758860a69d/query

https://api.cloudflare.com/client/v4/accounts/4f6d1970bc967b2c2a90b643bbb5ac94/d1/database/0e35121-f3cc-4e24-b5c1-4d758860a69d/query

https://api.cloudflare.com/client/v4/accounts/4f6d1970bc967b2c2a90b643bbb5ac94/d1/database/0e35121-f3cc-4e24-b5c1-4d758860a69d/query

https://api.cloudflare.com/client/v4/accounts/4f6d1970bc967b2c2a90b643bbb5ac94/d1/database/0e35121-f3cc-4e24-b5c1-4d758860a69d/query

K

kian•2/28/24, 3:53 PM

and if you log

options

options

then you see

Authorization: Bearer ...

Authorization: Bearer ...

Authorization: Bearer ...

Authorization: Bearer ...?

M

Mongy•2/28/24, 3:53 PM

the account id came from the pages/workers overview dashboard

K

kian•2/28/24, 3:53 PM

It all seems fine, the error is pretty vague.

M

Mongy•2/28/24, 3:53 PM

yes i see the bearer when logging

Kkian It all seems fine, the error is pretty vague.

M

Mongy•2/28/24, 3:54 PM

Yeah that's why I've come here to see if anyone has experienced something similar. It is offly vague

Original message was deleted

M

Mongy•2/28/24, 4:11 PM

the uuid matches to what im putting in the url

Original message was deleted

M

Mongy•2/28/24, 4:19 PM

Still receiving the same message

M

Mongy•2/28/24, 4:22 PM

const D1URL = 'https://api.cloudflare.com/client/v4/accounts/4f6d1970bc967b2c2a90b643bbb5ac94/d1/database/0e35121-f3cc-4e24-b5c1-4d758860a69d/query';

const insertStatement = `INSERT INTO table (c1, c2, c3) VALUES (v1, v2, v3)`;

const options = {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      Authorization: 'Bearer GAQjclxUayPOaHhn5Nx1CGdyN2Pt08COkmFTFBjm'
    },
    body: JSON.stringify({
      sql: insertStatement
    })
  }

fetch(D1URL, options)
    .then( res => res.json())
    .then( data => console.log(data))

const D1URL = 'https://api.cloudflare.com/client/v4/accounts/4f6d1970bc967b2c2a90b643bbb5ac94/d1/database/0e35121-f3cc-4e24-b5c1-4d758860a69d/query';

const insertStatement = `INSERT INTO table (c1, c2, c3) VALUES (v1, v2, v3)`;

const options = {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      Authorization: 'Bearer GAQjclxUayPOaHhn5Nx1CGdyN2Pt08COkmFTFBjm'
    },
    body: JSON.stringify({
      sql: insertStatement
    })
  }

fetch(D1URL, options)
    .then( res => res.json())
    .then( data => console.log(data))

const D1URL = 'https://api.cloudflare.com/client/v4/accounts/4f6d1970bc967b2c2a90b643bbb5ac94/d1/database/0e35121-f3cc-4e24-b5c1-4d758860a69d/query';

const insertStatement = `INSERT INTO table (c1, c2, c3) VALUES (v1, v2, v3)`;

const options = {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      Authorization: 'Bearer GAQjclxUayPOaHhn5Nx1CGdyN2Pt08COkmFTFBjm'
    },
    body: JSON.stringify({
      sql: insertStatement
    })
  }

fetch(D1URL, options)
    .then( res => res.json())
    .then( data => console.log(data))

const D1URL = 'https://api.cloudflare.com/client/v4/accounts/4f6d1970bc967b2c2a90b643bbb5ac94/d1/database/0e35121-f3cc-4e24-b5c1-4d758860a69d/query';

const insertStatement = `INSERT INTO table (c1, c2, c3) VALUES (v1, v2, v3)`;

const options = {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      Authorization: 'Bearer GAQjclxUayPOaHhn5Nx1CGdyN2Pt08COkmFTFBjm'
    },
    body: JSON.stringify({
      sql: insertStatement
    })
  }

fetch(D1URL, options)
    .then( res => res.json())
    .then( data => console.log(data))

M

Mongy•2/28/24, 4:23 PM

just simplified the insert statement

M

Mongy•2/28/24, 4:24 PM

already did when i realized lol

M

Mongy•2/28/24, 4:25 PM

but the api token has both read and write permissions for d1 instance

M

Mongy•2/28/24, 4:25 PM

they are actual strings

M

Mongy•2/28/24, 4:25 PM

i just renamed them

M

Mongy•2/28/24, 4:26 PM

i ran the same sql directly through the d1 dashboard

M

Mongy•2/28/24, 4:26 PM

and populated just fine

M

Mongy•2/28/24, 4:26 PM

same one im using in this script, not the one i posted here

M

Mongy•2/28/24, 4:27 PM

its an id problem but its not specifying what id its trying to decode

K

kian•2/28/24, 4:30 PM

Your DB ID is wrong

K

kian•2/28/24, 4:30 PM

It isn't formatted properly

K

kian•2/28/24, 4:30 PM

Yeah

K

kian•2/28/24, 4:30 PM

It's 7-4-4-4-12 when it should be 8-4-4-4-12

K

kian•2/28/24, 4:31 PM

Probably the first letter got cut off when copying

M

Mongy•2/28/24, 4:36 PM

That did the job

M

Mongy•2/28/24, 4:37 PM

I appreciate it

K

kian•2/28/24, 4:38 PM

@Max (@rozenmd) I'm not sure if the error is thrown by the API gateway before it gets to D1's REST API, but it'd be cool if the "failed to decode id" error could be more detailed even if it just calls out which ID it's upset with - d1-database

M

Max (@rozenmd)•2/28/24, 4:39 PM

ah yeah nah that's the rust uuid parser

M

Max (@rozenmd)•2/28/24, 4:39 PM

we'll be fixing this

S

Sébastien Morel•2/28/24, 7:48 PM

hello here I know we are still in beta with D1 but I just want to see if that makes sense. Without D1 I have 40ms latency on my worker, as soon as I do a query (simple select on an ID that has an index) it goes to 400ms... like 10x... am I doing something wrong ?

A

Aaryan•2/28/24, 8:03 PM

Guys my d1

f19f4e90-2514-4f2f-9d09-13ece5212673

f19f4e90-2514-4f2f-9d09-13ece5212673

f19f4e90-2514-4f2f-9d09-13ece5212673

f19f4e90-2514-4f2f-9d09-13ece5212673 is down. I really need it back for my presentation at uni tomorrow. Is there a time frame? or should I make another?

Original message was deleted

S

Sébastien Morel•2/28/24, 8:04 PM

that's something I don't know how to check, where is the DB ?

S

Sébastien Morel•2/28/24, 8:05 PM

here is an example of meta @nora

"result": {
"success": true,
"meta": {
"served_by": "v3-prod",
"duration": 0.1743,
"changes": 0,
"last_row_id": 0,
"changed_db": false,
"size_after": 25100288,
"rows_read": 1804,
"rows_written": 0
},
"results": [
{
"COUNT(*)": 1804
}
]

"result": {
"success": true,
"meta": {
"served_by": "v3-prod",
"duration": 0.1743,
"changes": 0,
"last_row_id": 0,
"changed_db": false,
"size_after": 25100288,
"rows_read": 1804,
"rows_written": 0
},
"results": [
{
"COUNT(*)": 1804
}
]

"result": {
"success": true,
"meta": {
"served_by": "v3-prod",
"duration": 0.1743,
"changes": 0,
"last_row_id": 0,
"changed_db": false,
"size_after": 25100288,
"rows_read": 1804,
"rows_written": 0
},
"results": [
{
"COUNT(*)": 1804
}
]

"result": {
"success": true,
"meta": {
"served_by": "v3-prod",
"duration": 0.1743,
"changes": 0,
"last_row_id": 0,
"changed_db": false,
"size_after": 25100288,
"rows_read": 1804,
"rows_written": 0
},
"results": [
{
"COUNT(*)": 1804
}
]

S

Sébastien Morel•2/28/24, 8:05 PM

383ms to get it

S

Sébastien Morel•2/28/24, 8:09 PM

wrangler d1 info

S

Sébastien Morel•2/28/24, 8:09 PM

got it so same region with my worker checking the header CF-Placement

S

Sébastien Morel•2/28/24, 8:11 PM

also for SELECT query is it not supposed to be distributed?

AAaryan Guys my d1 `f19f4e90-2514-4f2f-9d09-13ece5212673` is down. I really need it back...

A

Aaryan•2/28/24, 8:22 PM

seems to be back

Hello! Is it an expected behavior for an UPDATE query to always take 1 rows_read?

Similar Threads

Similar Threads

Similar Threads