CF doesn't tell us why, one said to stop using the product, we just can't connect to the db

Bbenthecarman CF doesn't tell us why, one said to stop using the product, we just can't connec...

C

captain•9/25/23, 1:11 AM

what region are you hinting with? I'm still on alpha but haven't had any downtime...ever. Was going to move it to beta DB today.

B

benthecarmanOP•9/25/23, 1:12 AM

we have people globally

Bbenthecarman we have people globally

C

captain•9/25/23, 1:12 AM

got it

C

captain•9/25/23, 1:13 AM

well hopefully they are seeing your bugs

B

benthecarmanOP•9/25/23, 1:13 AM

half the time they were unaware their system was down lol

C

captain•9/25/23, 1:16 AM

D1 is a game changer and so is workers, god speed!

B

benthecarmanOP•9/25/23, 1:16 AM

it would have been perfect for our usecase if it actually worked

C

captain•9/25/23, 1:18 AM

it wil be perfect for many, but what they are attempting to accomplish is super difficult, but workers is pretty amazing, kv is pretty solid, so just gotta be patient with the bleeding edge tech. I'm attempting to rewrite things from KV to D1 to shadow what I am doing with KV, but i'm still leaving KV as the baseline till D1 is out of ALpha/beta

C

captain•9/25/23, 1:19 AM

but perhaps if you need it now, you should be exploring durable objects more with nosql

Bbenthecarman I wouldn't use d1, it only has like 20% uptime

M

Matt Silverlock•9/25/23, 1:27 AM

This has been one of the very rare cases where we’ve seen this — it’s certainly not 20% (or even 5%). I get that you’re frustrated from your experience with D1, but 20% isn’t true.

MMatt Silverlock This has been one of the very rare cases where we’ve seen this — it’s certainly ...

C

captain•9/25/23, 1:43 AM

are you finding the version alpha or beta is currently more stable?

Ccaptain are you finding the version alpha or beta is currently more stable?

M

Matt Silverlock•9/25/23, 1:46 AM

The new storage subsystem is substantially more reliable and has been for months.

M

Matt Silverlock•9/25/23, 1:46 AM

(That’s why we made it the default)

MMatt Silverlock (That’s why we made it the default)

C

captain•9/25/23, 1:47 AM

copy that...in the midst of transfering over now

C

captain•9/25/23, 1:47 AM

enjoying being around for the cloudflare ride!

A

Adi•9/25/23, 3:18 AM

Genuinely can't wait to see what's announced for birthday week!
Hopefully some news around D1 as well

S

Santa DCON 🎄•9/25/23, 3:29 AM

D1 is actually shockingly amazing, I'm excited to move my everything to it as soon as it's production ready. Amazing work team!

AAdi Genuinely can't wait to see what's announced for birthday week! Hopefully some n...

S

Sameer Ali•9/25/23, 3:54 AM

When is the birthday week? just curious

S

Sameer Ali•9/25/23, 3:55 AM

I have been using D1 for long time, love the experience so far. Cloudflare Team is doing Excellent Job

SSameer Ali When is the birthday week? just curious

A

Adi•9/25/23, 3:58 AM

I believe it's this week

Expect quite a few announcements/blogs from Cloudflare

J

jb•9/25/23, 4:11 AM

https://blog.cloudflare.com/welcome-to-birthday-week-2023/

The Cloudflare Blog

Welcome to Birthday Week 2023

Building the future is, in part, what Birthday Week is about. Over the past 13 years we’ve announced things like Universal SSL (doubling the size of the encrypted web overnight), or Cloudflare Workers (helping change the way people build and scale applications). This year will be no different

D

divby0•9/25/23, 12:08 PM

Which orm do you people use with d1? I am so in love with how prisma allows you to query stuff, I don't want to go back to SQL-esque queries. But prisma doesn't work with d1 (yet). I tried drizzle whihc is the next best thing I have discovered, but I'd definitely like to try something more prisma-like

A

Adi•9/25/23, 12:47 PM

I can't recommend Drizzle enough, it's amazing. But it's syntax is definitely more SQL like.
That being said drizzle now has relationship like queries, so maybe it'll work for you.

B

boywonder350•9/25/23, 3:17 PM

I am hoping d1 goes to production soon so there is no 500mb limit

C

captain•9/25/23, 3:54 PM

I am diving in D1 again, previously was using a D1 alpha and now resetting things up with a D1 beta. Everything seems in order, however now I'm making my first entry and for some reason when it gets to the D1 code section...it doesn't get past it and the console log i have set to print after is not being printed.

1. Is the TOML set up any different
2. https://developers.cloudflare.com/d1/learning/debug-d1/ for the debug statement uses: e: any which is typescript only, for js should it just be e for the catch area (which is what I have now and is not showing anything)

thanks!

Debug D1 · Cloudflare D1 docs

D1 allows you to capture exceptions and log errors returned when querying a database. To debug D1, you will use the same tools available when …

C

captain•9/25/23, 3:57 PM

(also runing 3.6 , should probably change that)

Ccaptain I am diving in D1 again, previously was using a D1 alpha and now resetting thing...

M

Matt Silverlock•9/25/23, 4:06 PM

Can you share what your config is? There's no changes to how

wrangler.toml

wrangler.toml

works. Is this a Workers or a Pages project?

Ccaptain I am diving in D1 again, previously was using a D1 alpha and now resetting thing...

M

Matt Silverlock•9/25/23, 4:06 PM

Sharing your Workers code would be great too.

C

captain•9/25/23, 4:10 PM

    console.log("we start the new DB");
    try {
      console.log("we start the new DB test 1");
      await env.DBNAME_DB.prepare(`insert into messages (location_id,time_stamp,status,customer_dismiss) values (?,?,?,?)`).bind(restaurant_token_used, timestamp_index, 'new', 0).run()
      console.log("we start the new DB test 2");
    } catch (e) {
      console.log("we start the new DB test 3");
      console.log({
        message: e.message,
        cause: e.cause.message,
      });
    }
    console.log("we end the new DB");

    console.log("we start the new DB");
    try {
      console.log("we start the new DB test 1");
      await env.DBNAME_DB.prepare(`insert into messages (location_id,time_stamp,status,customer_dismiss) values (?,?,?,?)`).bind(restaurant_token_used, timestamp_index, 'new', 0).run()
      console.log("we start the new DB test 2");
    } catch (e) {
      console.log("we start the new DB test 3");
      console.log({
        message: e.message,
        cause: e.cause.message,
      });
    }
    console.log("we end the new DB");

    console.log("we start the new DB");
    try {
      console.log("we start the new DB test 1");
      await env.DBNAME_DB.prepare(`insert into messages (location_id,time_stamp,status,customer_dismiss) values (?,?,?,?)`).bind(restaurant_token_used, timestamp_index, 'new', 0).run()
      console.log("we start the new DB test 2");
    } catch (e) {
      console.log("we start the new DB test 3");
      console.log({
        message: e.message,
        cause: e.cause.message,
      });
    }
    console.log("we end the new DB");

    console.log("we start the new DB");
    try {
      console.log("we start the new DB test 1");
      await env.DBNAME_DB.prepare(`insert into messages (location_id,time_stamp,status,customer_dismiss) values (?,?,?,?)`).bind(restaurant_token_used, timestamp_index, 'new', 0).run()
      console.log("we start the new DB test 2");
    } catch (e) {
      console.log("we start the new DB test 3");
      console.log({
        message: e.message,
        cause: e.cause.message,
      });
    }
    console.log("we end the new DB");

C

captain•9/25/23, 4:13 PM

and in the TOML file:
d1_databases = [
{ binding = "DBNAME_DB", database_name = "DBNAME_DB", database_id = "74244d9f-afa8-4ca2-ab7f-NEWID" }, #{ binding = "DBNAME_DB", database_name = "DBNAME_DB", database_id = "e6cf047a-8ce0-41a9-a47e-OLDID" },
]

C

captain•9/25/23, 4:14 PM

I am placing this just below where I set my kv_namespaces = [] stuff.

C

captain•9/25/23, 4:22 PM

the expectation would be it should display some error if getting here, but for some reason its like a black hole

C

captain•9/25/23, 4:40 PM

I lowered the position of where d1_databases = is in the toml file (just below my [vars] and now I can see the try getting catched

C

captain•9/25/23, 4:40 PM

but when printing out the: "e" it's empty

Ccaptain ``` console.log("we start the new DB"); try { console.log("we start...

M

Matt Silverlock•9/25/23, 4:58 PM

Can you run just a very basic query - start from scratch. Just

await db.exec("PRAGMA table_list")

await db.exec("PRAGMA table_list")

- and nothing else? Your binding appears fine. You aren't returning any results (because it's an INSERT without any RETURNING) - what do you expect to happen? It should just insert without an error.

U

Unsmart•9/25/23, 5:01 PM

Defining you d1_databases array under a

[vars]

[vars]

table will make it where your D1 bindings are not defined unless you changed your format to use a table for

d1_databases

d1_databases

also which is why you started to get an error when you moved it.

These 2 toml files are not equal:

d1_databases = [
  { binding = "name", ... }
]

[vars]
hello = "world"

d1_databases = [
  { binding = "name", ... }
]

[vars]
hello = "world"

d1_databases = [
  { binding = "name", ... }
]

[vars]
hello = "world"

d1_databases = [
  { binding = "name", ... }
]

[vars]
hello = "world"

[vars]
hello = "world"

d1_databases = [
  { binding = "name", ... }
]

[vars]
hello = "world"

d1_databases = [
  { binding = "name", ... }
]

[vars]
hello = "world"

d1_databases = [
  { binding = "name", ... }
]

[vars]
hello = "world"

d1_databases = [
  { binding = "name", ... }
]

UUnsmart Defining you d1_databases array under a `[vars]` table will make it where your D...

C

captain•9/25/23, 5:04 PM

thanks for that, yes I noticed that when review:
"Your worker has access to the following bindings:"
when i was deploying. That said , same results in every scenario.

MMatt Silverlock Can you run just a very basic query - start from scratch. Just `await db.exec("P...

C

captain•9/25/23, 5:05 PM

I will try that real quick, I expect to insert the row and then get to the next section of code, however for some reason it just stops and doesn't get past the try catch.

MMatt Silverlock Can you run just a very basic query - start from scratch. Just `await db.exec("P...

C

captain•9/25/23, 5:05 PM

i'm avail for vid chat if you want me to walk you through this little bit of code if helps uncover a bug

MMatt Silverlock Can you run just a very basic query - start from scratch. Just `await db.exec("P...

C

captain•9/25/23, 5:13 PM

i'm running:

var coolio200 = await env.MYDATABASE_DB.exec("PRAGMA table_list")
console.log("here is coolio100")
console.log("here is coolio200: " + JSON.stringify(coolio200))

var coolio200 = await env.MYDATABASE_DB.exec("PRAGMA table_list")
console.log("here is coolio100")
console.log("here is coolio200: " + JSON.stringify(coolio200))

var coolio200 = await env.MYDATABASE_DB.exec("PRAGMA table_list")
console.log("here is coolio100")
console.log("here is coolio200: " + JSON.stringify(coolio200))

var coolio200 = await env.MYDATABASE_DB.exec("PRAGMA table_list")
console.log("here is coolio100")
console.log("here is coolio200: " + JSON.stringify(coolio200))

and it doesn't print out the console log, it just stops

C

captain•9/25/23, 5:14 PM

when I deploy I can see in the log as it deploys:

- KV Namespaces:
....
- D1 Databases:
  - MYDATABASE_DB: mydbinmydashboard (74244d9f-afa8-4ca2-ab7f-XXXXXX)
- Vars:
.....

- KV Namespaces:
....
- D1 Databases:
  - MYDATABASE_DB: mydbinmydashboard (74244d9f-afa8-4ca2-ab7f-XXXXXX)
- Vars:
.....

- KV Namespaces:
....
- D1 Databases:
  - MYDATABASE_DB: mydbinmydashboard (74244d9f-afa8-4ca2-ab7f-XXXXXX)
- Vars:
.....

- KV Namespaces:
....
- D1 Databases:
  - MYDATABASE_DB: mydbinmydashboard (74244d9f-afa8-4ca2-ab7f-XXXXXX)
- Vars:
.....

M

Matt Silverlock•9/25/23, 5:39 PM

https://gist.github.com/elithrar/73e7340046a397ce427d45c037347d1c - this works as-is.

MMatt Silverlock https://gist.github.com/elithrar/73e7340046a397ce427d45c037347d1c - this works a...

C

captain•9/25/23, 5:50 PM

do you have example from .js code and not .ts

C

captain•9/25/23, 5:50 PM

i notice in other places of documentation it shows a toggle betweent the two

C

captain•9/25/23, 5:50 PM

and do u test with .js

MMatt Silverlock https://gist.github.com/elithrar/73e7340046a397ce427d45c037347d1c - this works a...

C

captain•9/25/23, 5:52 PM

with my js code the way I am binding things is different for the differnt env scenarios and I think its worth using that as an example as I think its more common

Ccaptain with my js code the way I am binding things is different for the differnt env sc...

M

Matt Silverlock•9/25/23, 5:55 PM

Share your full Worker. Are you sure you're naming the variables correctly? Are you using the same Worker format as I've shown?

Ccaptain with my js code the way I am binding things is different for the differnt env sc...

M

Matt Silverlock•9/25/23, 5:56 PM

export default {
    async fetch(request, env, ctx) {
        let res = await env.MYDATABASE.exec("PRAGMA table_list")
        console.log(res)
        return Response.json({res: res})
    },
};

export default {
    async fetch(request, env, ctx) {
        let res = await env.MYDATABASE.exec("PRAGMA table_list")
        console.log(res)
        return Response.json({res: res})
    },
};

export default {
    async fetch(request, env, ctx) {
        let res = await env.MYDATABASE.exec("PRAGMA table_list")
        console.log(res)
        return Response.json({res: res})
    },
};

export default {
    async fetch(request, env, ctx) {
        let res = await env.MYDATABASE.exec("PRAGMA table_list")
        console.log(res)
        return Response.json({res: res})
    },
};

(TypeScript is transpiled into JavaScript before it is deployed, so there should be no difference)

CF doesn't tell us why, one said to stop using the product, we just can't connect to the db

Similar Threads

Similar Threads

Similar Threads