Read replicas, Backups, Larger DB Storage, and Dynamic Bindings have all been said to be coming by G

UUnsmart Read replicas, Backups, Larger DB Storage, and Dynamic Bindings have all been sa...

M

Bear in mind that the linked comments are not promises - "we'd like to"/"it's planned" !== coming by date X with certainty

U

UnsmartOP•2/27/24, 5:45 PM

Dynamic bindings did say "will be part of/ahead of GA"

U

UnsmartOP•2/27/24, 5:46 PM

but yes

UUnsmart Dynamic bindings did say "will be part of/ahead of GA" 😛

M

Matt Silverlock•2/27/24, 5:49 PM

Still not promises. Team is working on shipping a lot, and we want to be transparent with timelines, but these are not guarantees.

MMatt Silverlock Still not promises. Team is working on shipping a lot, and we want to be transpa...

E

Epailes•2/27/24, 7:06 PM

Good to know it's at least up there on the priority list even if it doesn't end up making GA!

UUnsmart Read replicas, Backups, Larger DB Storage, and Dynamic Bindings have all been sa...

B

bun•2/27/24, 9:55 PM

what does GA mean?

Bbun what does GA mean?

U

UnsmartOP•2/27/24, 9:55 PM

generally available aka production ready

B

bun•2/27/24, 9:56 PM

so they just mean that those features will be available once its production ready ? like not in beta?

U

UnsmartOP•2/27/24, 9:56 PM

Yes, and its more of a plan to have them so it might be ready might be after

B

bun•2/27/24, 9:57 PM

ok but why does this not work

await this.db.batch([
      this.db.insert(blobs).values({ hash: blobHash }),
      this.db
        .insert(assets)
        .values({ projectId, blobId: sql`last_insert_rowid()` })
        .returning({ assetId: assets.id }),
    ]);

await this.db.batch([
      this.db.insert(blobs).values({ hash: blobHash }),
      this.db
        .insert(assets)
        .values({ projectId, blobId: sql`last_insert_rowid()` })
        .returning({ assetId: assets.id }),
    ]);

await this.db.batch([
      this.db.insert(blobs).values({ hash: blobHash }),
      this.db
        .insert(assets)
        .values({ projectId, blobId: sql`last_insert_rowid()` })
        .returning({ assetId: assets.id }),
    ]);

await this.db.batch([
      this.db.insert(blobs).values({ hash: blobHash }),
      this.db
        .insert(assets)
        .values({ projectId, blobId: sql`last_insert_rowid()` })
        .returning({ assetId: assets.id }),
    ]);

    [cause]: Error: FOREIGN KEY constraint failed

[cause]: Error: FOREIGN KEY constraint failed

    [cause]: Error: FOREIGN KEY constraint failed

[cause]: Error: FOREIGN KEY constraint failed
like what

U

UnsmartOP•2/27/24, 9:57 PM

No clue I dont use SQL

B

bun•2/27/24, 9:57 PM

what do you use then

U

UnsmartOP•2/27/24, 9:57 PM

On cloudflare I use durable objects :NODDER:

B

bun•2/27/24, 10:00 PM

idk i couuldnt ever get used to workin with durable objects. they seem great at first but even for a simple key value store i have to write a class? like what

B

bun•2/27/24, 10:01 PM

yeah its probably the

blobId

blobId

blobId

blobId, but shouldnt

last_insert_rowid()

last_insert_rowid()

last_insert_rowid()

last_insert_rowid() return the

id

id

id

id of the latest inserted

blob

blob

blob

blob ? as in the first batch statement?

B

bun•2/27/24, 10:02 PM

B

bun•2/27/24, 10:03 PM

do you prefer raw sql ?

B

bun•2/27/24, 10:03 PM

CREATE TABLE `assets` (
    `id` integer PRIMARY KEY AUTOINCREMENT NOT NULL,
    `ref_count` integer DEFAULT 1 NOT NULL,
    `blob_id` integer NOT NULL,
    `user_id` integer NOT NULL,
    `created_at` integer DEFAULT (CURRENT_TIMESTAMP) NOT NULL,
    FOREIGN KEY (`blob_id`) REFERENCES `blobs`(`id`) ON UPDATE cascade ON DELETE restrict,
    FOREIGN KEY (`user_id`) REFERENCES `users`(`id`) ON UPDATE cascade ON DELETE restrict
);

CREATE TABLE `blobs` (
    `id` integer PRIMARY KEY AUTOINCREMENT NOT NULL,
    `hash` text NOT NULL
);

CREATE TABLE `assets` (
    `id` integer PRIMARY KEY AUTOINCREMENT NOT NULL,
    `ref_count` integer DEFAULT 1 NOT NULL,
    `blob_id` integer NOT NULL,
    `user_id` integer NOT NULL,
    `created_at` integer DEFAULT (CURRENT_TIMESTAMP) NOT NULL,
    FOREIGN KEY (`blob_id`) REFERENCES `blobs`(`id`) ON UPDATE cascade ON DELETE restrict,
    FOREIGN KEY (`user_id`) REFERENCES `users`(`id`) ON UPDATE cascade ON DELETE restrict
);

CREATE TABLE `blobs` (
    `id` integer PRIMARY KEY AUTOINCREMENT NOT NULL,
    `hash` text NOT NULL
);

CREATE TABLE `assets` (
    `id` integer PRIMARY KEY AUTOINCREMENT NOT NULL,
    `ref_count` integer DEFAULT 1 NOT NULL,
    `blob_id` integer NOT NULL,
    `user_id` integer NOT NULL,
    `created_at` integer DEFAULT (CURRENT_TIMESTAMP) NOT NULL,
    FOREIGN KEY (`blob_id`) REFERENCES `blobs`(`id`) ON UPDATE cascade ON DELETE restrict,
    FOREIGN KEY (`user_id`) REFERENCES `users`(`id`) ON UPDATE cascade ON DELETE restrict
);

CREATE TABLE `blobs` (
    `id` integer PRIMARY KEY AUTOINCREMENT NOT NULL,
    `hash` text NOT NULL
);

CREATE TABLE `assets` (
    `id` integer PRIMARY KEY AUTOINCREMENT NOT NULL,
    `ref_count` integer DEFAULT 1 NOT NULL,
    `blob_id` integer NOT NULL,
    `user_id` integer NOT NULL,
    `created_at` integer DEFAULT (CURRENT_TIMESTAMP) NOT NULL,
    FOREIGN KEY (`blob_id`) REFERENCES `blobs`(`id`) ON UPDATE cascade ON DELETE restrict,
    FOREIGN KEY (`user_id`) REFERENCES `users`(`id`) ON UPDATE cascade ON DELETE restrict
);

CREATE TABLE `blobs` (
    `id` integer PRIMARY KEY AUTOINCREMENT NOT NULL,
    `hash` text NOT NULL
);

B

bun•2/27/24, 10:06 PM

hm

B

bun•2/27/24, 10:07 PM

ah ye. i renamed the column to project_id without changing the reference. i will fix that and see if the issue's still thare

B

Beyondo•2/28/24, 2:33 PM

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

Max (@rozenmd)•2/28/24, 3:05 PM

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

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

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

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

Read replicas, Backups, Larger DB Storage, and Dynamic Bindings have all been said to be coming by G

Similar Threads

Similar Threads

Similar Threads