https://github.com/cloudflare/cloudflare-docs/pull/9298 incoming 🙂

MMatt Silverlock https://github.com/cloudflare/cloudflare-docs/pull/9298 incoming 🙂

I

I just changed my code to show

error.cause

error.cause

error.cause

error.cause lul

Iitsmatteomanf I just changed my code to show `error.cause` <:lul:946531054485930015>

M

Matt SilverlockOP•6/8/23, 8:54 PM

We’ll intend to keep that as is for a bit, but it’s an overdue change. Doesn’t matter that

.cause

.cause

.cause

.cause is standard, unfortunately

MMatt Silverlock We’ll intend to keep that as is for a bit, but it’s an overdue change. Doesn’t m...

I

itsmatteomanf•6/8/23, 8:55 PM

Oh yeah, don't worry... I was one of the people not using it until you told me lul

OOr according to the docs it looks like the maximum arguments per SQL function was b...

M

Matt SilverlockOP•6/9/23, 12:18 AM

No, the docs just got ahead of the release. Still 8.

L

lokiwind•6/9/23, 12:09 PM

Hello, I would like to establish a connection between workers and mongodb, is there a tutorial on this?

MMatt Silverlock Not at the moment, no: not something we yet expose.

M

Murder Chicken•6/9/23, 12:13 PM

Is there any work around to, locally, somehow inspect what the end query result is with the bindings applied? It's super hard to debug queries if they're working directly in the DB but failing when D1 is trying to apply a bind. Any way to replicate what's under the hood in a custom debug function?

M

Murder Chicken•6/9/23, 12:34 PM

I see what's up now that I'm looking at the facade. The statement and bindings are sent to sqlite so there is no local interpolation. Anyway way to log d1 queries at the database level?

M

Max (@rozenmd)•6/9/23, 1:11 PM

Drizzle has a way of letting you see the actual query it runs, I don't think we have that as part of D1 yet

M

Murder Chicken•6/9/23, 1:20 PM

Does Drizzle even work properly with D1? I was seeing posts around people having to jump through hoops to get it to work.

M

Max (@rozenmd)•6/9/23, 1:26 PM

It works, it just has column name collisions when joining tables with the same column names + not using aliases

M

Murder Chicken•6/9/23, 1:27 PM

Ok, thanks @rozenmd , will take a look. Feels like overkill to debug a query with an ORM, haha.

Original message was deleted

M

Murder Chicken•6/9/23, 2:31 PM

Unfortunately, it's not that simple. Dumping the statement and bindings gives you the component pieces but does not allow you to introspect how they're being married together to form a complete query.

In this instance (just solved it), an integer value was being bound to the query as a string. I had to explicitly cast that particular parameter value with

parseInt

parseInt

parseInt

parseInt to get the query to function. Figuring it out through process of elimination is time-consuming and I ended up having to remove bound parameters one by one until I identified which one was causing the issue so that I could trace back why that value was being bound improperly.

Llokiwind Hello, I would like to establish a connection between workers and mongodb, is th...

I

Isaac McFadyen•6/9/23, 3:33 PM

This isn't really #d1-open-alpha specific, so I'd recommend we move to #workers-discussions.

OOr according to the docs it looks like the maximum arguments per SQL function was b...

M

Matt SilverlockOP•6/9/23, 4:06 PM

Released: all functions now accept up to 32 arguments.

➜  wrangler d1 execute db-enam --command "SELECT json_object('hello', 1, 'world', 2, 'foo', 3, 'bar', 4, 'baz', 5, 'quux', 6, 'floop', 7)"

🌀 Mapping SQL input into an array of statements
🌀 Parsing 1 statements
🚣 Executed 1 commands in 0.1332309991121292ms
┌──────────────────────────────────────────────────────────────────────────────────────────┐
│ json_object('hello', 1, 'world', 2, 'foo', 3, 'bar', 4, 'baz', 5, 'quux', 6, 'floop', 7) │
├──────────────────────────────────────────────────────────────────────────────────────────┤
│ {"hello":1,"world":2,"foo":3,"bar":4,"baz":5,"quux":6,"floop":7}                         │
└──────────────────────────────────────────────────────────────────────────────────────────┘

➜  wrangler d1 execute db-enam --command "SELECT json_object('hello', 1, 'world', 2, 'foo', 3, 'bar', 4, 'baz', 5, 'quux', 6, 'floop', 7)"

🌀 Mapping SQL input into an array of statements
🌀 Parsing 1 statements
🚣 Executed 1 commands in 0.1332309991121292ms
┌──────────────────────────────────────────────────────────────────────────────────────────┐
│ json_object('hello', 1, 'world', 2, 'foo', 3, 'bar', 4, 'baz', 5, 'quux', 6, 'floop', 7) │
├──────────────────────────────────────────────────────────────────────────────────────────┤
│ {"hello":1,"world":2,"foo":3,"bar":4,"baz":5,"quux":6,"floop":7}                         │
└──────────────────────────────────────────────────────────────────────────────────────────┘

➜  wrangler d1 execute db-enam --command "SELECT json_object('hello', 1, 'world', 2, 'foo', 3, 'bar', 4, 'baz', 5, 'quux', 6, 'floop', 7)"

🌀 Mapping SQL input into an array of statements
🌀 Parsing 1 statements
🚣 Executed 1 commands in 0.1332309991121292ms
┌──────────────────────────────────────────────────────────────────────────────────────────┐
│ json_object('hello', 1, 'world', 2, 'foo', 3, 'bar', 4, 'baz', 5, 'quux', 6, 'floop', 7) │
├──────────────────────────────────────────────────────────────────────────────────────────┤
│ {"hello":1,"world":2,"foo":3,"bar":4,"baz":5,"quux":6,"floop":7}                         │
└──────────────────────────────────────────────────────────────────────────────────────────┘

➜  wrangler d1 execute db-enam --command "SELECT json_object('hello', 1, 'world', 2, 'foo', 3, 'bar', 4, 'baz', 5, 'quux', 6, 'floop', 7)"

🌀 Mapping SQL input into an array of statements
🌀 Parsing 1 statements
🚣 Executed 1 commands in 0.1332309991121292ms
┌──────────────────────────────────────────────────────────────────────────────────────────┐
│ json_object('hello', 1, 'world', 2, 'foo', 3, 'bar', 4, 'baz', 5, 'quux', 6, 'floop', 7) │
├──────────────────────────────────────────────────────────────────────────────────────────┤
│ {"hello":1,"world":2,"foo":3,"bar":4,"baz":5,"quux":6,"floop":7}                         │
└──────────────────────────────────────────────────────────────────────────────────────────┘

Iitsmatteomanf Done, https://github.com/cloudflare/workerd/issues/729

M

Matt SilverlockOP•6/9/23, 4:14 PM

We just merged this internally. Had to do a bunch of work on our storage layer to make this work correctly. Goal is to get

ALTER TABLE

ALTER TABLE

ALTER TABLE

ALTER TABLE statements released within the week or so.

JJacob Wright I'm getting "not authorized to use function" with timestamp functions (e.g. SELE...

M

Matt SilverlockOP•6/9/23, 4:16 PM

All of

current_timestamp

current_timestamp

current_timestamp

current_timestamp,

current_time

current_time

current_time

current_time, and

current_date

current_date

current_date

current_date should now work outside of

CREATE TABLE

CREATE TABLE

statements now:

➜  wrangler d1 execute db-enam --command "SELECT current_timestamp, current_time, current_date" --json | jq '.[].results'
[
  {
    "current_timestamp": "2023-06-09 16:16:37",
    "current_time": "16:16:37",
    "current_date": "2023-06-09"
  }
]

➜  wrangler d1 execute db-enam --command "SELECT current_timestamp, current_time, current_date" --json | jq '.[].results'
[
  {
    "current_timestamp": "2023-06-09 16:16:37",
    "current_time": "16:16:37",
    "current_date": "2023-06-09"
  }
]

➜  wrangler d1 execute db-enam --command "SELECT current_timestamp, current_time, current_date" --json | jq '.[].results'
[
  {
    "current_timestamp": "2023-06-09 16:16:37",
    "current_time": "16:16:37",
    "current_date": "2023-06-09"
  }
]

➜  wrangler d1 execute db-enam --command "SELECT current_timestamp, current_time, current_date" --json | jq '.[].results'
[
  {
    "current_timestamp": "2023-06-09 16:16:37",
    "current_time": "16:16:37",
    "current_date": "2023-06-09"
  }
]

MMatt Silverlock We just merged this internally. Had to do a bunch of work on our storage layer t...

I

itsmatteomanf•6/9/23, 4:49 PM

Thank you, appreciated

MMatt Silverlock All of `current_timestamp`, `current_time`, and `current_date` should now work o...

I

itsmatteomanf•6/9/23, 4:50 PM

Oh hey, that was a thing I had pinged you about, too ahah

I

itstmillertime•6/9/23, 6:03 PM

How does one run a D1 database migration in CI/CD?
I am running the following:

wrangler d1 migrations apply production

wrangler d1 migrations apply production

wrangler d1 migrations apply production

wrangler d1 migrations apply production

But it wants a keyboard press `` to confirm the migration. Any advice is appreciated!

Iitstmillertime How does one run a D1 database migration in CI/CD? I am running the following: `...

M

Matt SilverlockOP•6/9/23, 6:17 PM

We need to accept the

-y

-y

-y

-y flag (not supported yet). You should be able to

echo | wrangler d1 migrations apply <db-name>

echo | wrangler d1 migrations apply <db-name>

echo | wrangler d1 migrations apply <db-name>

echo | wrangler d1 migrations apply <db-name> to non-interactively confirm

I

itstmillertime•6/9/23, 6:42 PM

@skye_31 What's the CI environment variable? CI=true?

MMatt Silverlock We need to accept the `-y` flag (not supported yet). You should be able to `echo...

I

itstmillertime•6/9/23, 6:42 PM

Wrapping it in an echo pipe is the secret?

Iitstmillertime @skye_31 What's the CI environment variable? CI=true?

M

Max (@rozenmd)•6/9/23, 6:47 PM

it should support these: https://github.com/watson/ci-info#supported-ci-tools

M

Max (@rozenmd)•6/9/23, 6:48 PM

otherwise hardcoding CI=1 or CI=true works

K

kian•6/9/23, 7:45 PM

It just means you didn't call

all()

all()

all()

all()/

raw()

raw()

raw()

raw()/

first()

first()

first()

first()/etc

K

kian•6/9/23, 7:45 PM

Execute returned results - did you mean to call query?

I

itsmatteomanf•6/9/23, 8:36 PM

Hey @rozenmd, I think it's you that handles UI bugs from the dash, right?
If you have a table with

table

table

as the name of a column, it fails to delete rows from the UI. I presume it isn't adding

'

' or

around column names.

I

itsmatteomanf•6/9/23, 8:37 PM

Not sure why it is specifying columns for row deletions, probably to select data?

M

marc•6/9/23, 11:43 PM

I've been trying out D1 recently paired with a Worker. How often are Reads and Writes updated on CF's dashboard? As it seems to be showing 0 for both even though I'm actively reading and writing from them.

Mmarc I've been trying out D1 recently paired with a Worker. How often are Reads and W...

M

Max (@rozenmd)•6/9/23, 11:56 PM

can be a few minutes - also I should add a tooltip that only experimental backend dbs have metrics

MMax (@rozenmd)can be a few minutes - also I should add a tooltip that only experimental backen...

M

marc•6/10/23, 12:01 AM

That makes sense - thank you ^^

MMatt Silverlock We just merged this internally. Had to do a bunch of work on our storage layer t...

I

itsmatteomanf•6/10/23, 10:12 PM

ALTER TABLE

ALTER TABLE

ALTER TABLE

ALTER TABLE works! party_yay

I

itsmatteomanf•6/10/23, 10:52 PM

But is

DROP COLUMN

DROP COLUMN

DROP COLUMN

DROP COLUMN supported? It's giving me a not authorized...

K

kian•6/10/23, 10:54 PM

Seems like it should be

I

itsmatteomanf•6/10/23, 11:03 PM

I tried both, and they both returned a "not authorized".

ALTER TABLE <table> DROP COLUMN <column>;
ALTER TABLE <table> DROP <column>;

ALTER TABLE <table> DROP COLUMN <column>;
ALTER TABLE <table> DROP <column>;

ALTER TABLE <table> DROP COLUMN <column>;
ALTER TABLE <table> DROP <column>;

ALTER TABLE <table> DROP COLUMN <column>;
ALTER TABLE <table> DROP <column>;

Iitsmatteomanf `ALTER TABLE` works! <a:party_yay:820426146024914955> 🎉

M

Matt SilverlockOP•6/11/23, 1:18 AM

It hasn’t shipped yet.

Kkian Seems like it should be

M

Matt SilverlockOP•6/11/23, 1:18 AM

Source != deployed.

MMatt Silverlock It hasn’t shipped yet.

I

itsmatteomanf•6/11/23, 1:39 AM

Ohhh, so some sections of

ALTER TABLE

ALTER TABLE

ALTER TABLE

ALTER TABLE did work already

I assumed it was fully blocked. Will wait

G

Garrett•6/12/23, 3:38 AM

What's the state of D1 these days? Guessing not feature/API stable and unsuitable for production use? Any ETAs on it?

GGarrett What's the state of D1 these days? Guessing not feature/API stable and unsuitabl...

M

Max (@rozenmd)•6/12/23, 8:37 AM

https://blog.cloudflare.com/d1-turning-it-up-to-11/

The Cloudflare Blog

D1: We turned it up to 11

We've been heads down iterating on D1, and we've just shipped a major new version that's substantially faster, more reliable, and introduces Time Travel: the ability to restore a D1 database to any point in time.