As pointed out above it’s an alpha product and you should not be using it for production. But haven’

UUnsmart As pointed out above it’s an alpha product and you should not be using it for pr...

B

benthecarman•9/23/23, 4:18 AM

The entire database is unreachable

U

UnsmartOP•9/23/23, 4:18 AM

What error are you getting?

B

benthecarman•9/23/23, 4:27 AM

it just times out, database wont even show in the UI

M

mrwind•9/23/23, 9:49 AM

Hi I am write a package to combine kysely and zod for working with json on D1 https://github.com/windwp/kysely-zod-sqlite

GitHub

GitHub - windwp/kysely-zod-sqlite: An flexible api for Cloudflare D...

An flexible api for Cloudflare D1 and sqlite. It has an simple api of Prisma and a powerful query with Kysely. - GitHub - windwp/kysely-zod-sqlite: An flexible api for Cloudflare D1 and sqlite. It ...

Ccaptain thanks! I'm using wrangler 3.6... guess I'll stick to 3.6 because this issue sca...

M

Matt Silverlock•9/23/23, 11:46 AM

That issue only impacts local mode for that user:

wrangler 3.9.0

wrangler 3.9.0

wrangler 3.9.0

wrangler 3.9.0 is the latest as well.

Bbenthecarman Hey, our database keeps going down, are we able to get any status updates on whe...

M

Matt Silverlock•9/23/23, 11:47 AM

Can you provide your database ID?

MMatt Silverlock That issue only impacts local mode for that user: `wrangler 3.9.0` is the latest...

C

captain•9/23/23, 4:45 PM

got it, so issue is addressed in 3.9?

C

captain•9/23/23, 4:47 PM

@Matt also seperate question. I have a digital ocean hosted non static django sqlite project that I have been meaning to give some attention to...do you think running it with D1 is possble now on cloudflare, or what would be some of the roadblocks still and do think the roadblocks would overcome in the future?

Ccaptain @Matt also seperate question. I have a digital ocean hosted non static django sq...

M

Matt Silverlock•9/23/23, 4:59 PM

Which specific roadblocks? It's up to each user to determine how comfortable they are with a beta product. We have teams at Cloudflare using D1 for production apps but it entirely depends on your use-case and the criticality of your application.

MMatt Silverlock Which specific roadblocks? It's up to each user to determine how comfortable the...

C

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

for instance, the built in authentication using sqlite database scenario would make it a non static site. Is there a roadblock or some sqlite functionality that is not possible in the cloudflare d1 iteration that is necessary for django to run. Another note from another thread somebody is mentioning that workers is JS and webassembly only. I have only usage with standard workers and very basic d1 ussuage in my project, in a learning phase for this area, any incite you can provide is helpful.

Ccaptain for instance, the built in authentication using sqlite database scenario would m...

M

Matt Silverlock•9/23/23, 5:07 PM

Django cannot talk to D1 directly: "SQLite" doesn't have the concept of a remote connection, because it's an embedded database. Django would need an adapter for D1.

Ccaptain for instance, the built in authentication using sqlite database scenario would m...

M

Matt Silverlock•9/23/23, 5:08 PM

e.g. that uses D1's HTTP API, or a Worker of your own: https://developers.cloudflare.com/api/operations/cloudflare-d1-query-database / https://github.com/elithrar/http-api-d1-example

Cloudflare API Documentation

Interact with Cloudflare's products and services via the Cloudflare API

GitHub

GitHub - elithrar/http-api-d1-example: An example HTTP API for Clou...

An example HTTP API for Cloudflare's D1 database: https://developers.cloudflare.com/d1/

GitHub - elithrar/http-api-d1-example: An example HTTP API for Cloudflare's D1 database: ht...

MMatt Silverlock e.g. that uses D1's HTTP API, or a Worker of your own: https://developers.cloudf...

C

captain•9/23/23, 5:10 PM

got it, interested will have to explore this more, thanks for that link. getting django using this library up and running would be a great demo

MMatt Silverlock Can you provide your database ID?

B

benthecarman•9/24/23, 4:42 AM

fba9bfa8-37e0-4c2f-a74c-4b466a2f4251

B

benthecarman•9/24/23, 4:42 AM

it's down again

C

conqr ᯅ•9/24/23, 11:05 AM

Is there any way to rollback a transaction (aka batch) if a select clause finds no results? Something like

BEGIN;

-- Check if a record with the specified car_id and owner_id exists in the cars table
DECLARE @car_matches INTEGER;
SET @car_matches = (SELECT COUNT(*) FROM cars WHERE car_id = 'car1' AND owner_id = 'bob');

-- Only insert into the tickets table if we find a match for that car and owner
IF @car_matches > 0 THEN
    -- Insert data into the tickets table
    INSERT INTO tickets (ticket_description, owner_id, car_id)
      VALUES ('Speeding', 'bob', 'car1');
ELSE
    -- The car does not exist, or the owner has changed
    ROLLBACK;
END IF;

COMMIT;

BEGIN;

-- Check if a record with the specified car_id and owner_id exists in the cars table
DECLARE @car_matches INTEGER;
SET @car_matches = (SELECT COUNT(*) FROM cars WHERE car_id = 'car1' AND owner_id = 'bob');

-- Only insert into the tickets table if we find a match for that car and owner
IF @car_matches > 0 THEN
    -- Insert data into the tickets table
    INSERT INTO tickets (ticket_description, owner_id, car_id)
      VALUES ('Speeding', 'bob', 'car1');
ELSE
    -- The car does not exist, or the owner has changed
    ROLLBACK;
END IF;

COMMIT;

BEGIN;

-- Check if a record with the specified car_id and owner_id exists in the cars table
DECLARE @car_matches INTEGER;
SET @car_matches = (SELECT COUNT(*) FROM cars WHERE car_id = 'car1' AND owner_id = 'bob');

-- Only insert into the tickets table if we find a match for that car and owner
IF @car_matches > 0 THEN
    -- Insert data into the tickets table
    INSERT INTO tickets (ticket_description, owner_id, car_id)
      VALUES ('Speeding', 'bob', 'car1');
ELSE
    -- The car does not exist, or the owner has changed
    ROLLBACK;
END IF;

COMMIT;

BEGIN;

-- Check if a record with the specified car_id and owner_id exists in the cars table
DECLARE @car_matches INTEGER;
SET @car_matches = (SELECT COUNT(*) FROM cars WHERE car_id = 'car1' AND owner_id = 'bob');

-- Only insert into the tickets table if we find a match for that car and owner
IF @car_matches > 0 THEN
    -- Insert data into the tickets table
    INSERT INTO tickets (ticket_description, owner_id, car_id)
      VALUES ('Speeding', 'bob', 'car1');
ELSE
    -- The car does not exist, or the owner has changed
    ROLLBACK;
END IF;

COMMIT;

C

conqr ᯅ•9/24/23, 11:05 AM

I know you can batch queries, but I don't believe there is a way to actually rollback the entire transaction outside of a SQL error

Cconqr ᯅ I know you can batch queries, but I don't believe there is a way to actually rol...

I

Isaac McFadyen•9/24/23, 11:05 AM

No. D1 doesn't support manual transactions, only the automatic transactions that occur when you send batch operations.

I

Isaac McFadyen•9/24/23, 11:06 AM

So no ROLLBACK aside from throwing an error inside a batch operation.

IIsaac McFadyen So no ROLLBACK aside from throwing an error inside a batch operation.

C

conqr ᯅ•9/24/23, 11:08 AM

Is there any way to use a conditional and then throw an error based off of that, or is that not supported

Bbenthecarman fba9bfa8-37e0-4c2f-a74c-4b466a2f4251

M

Matt Silverlock•9/24/23, 11:20 AM

Thanks: looking into why it's sticking.

Cconqr ᯅ Is there any way to use a conditional and then throw an error based off of that,...

M

Matt Silverlock•9/24/23, 11:21 AM

https://www.sqlite.org/lang_conflict.html can be very useful here

MMatt Silverlock https://www.sqlite.org/lang_conflict.html can be very useful here

C

conqr ᯅ•9/24/23, 11:38 AM

Are those statements supported though?

C

conqr ᯅ•9/24/23, 11:39 AM

I've resorted to using a combination

INSERT INTO ... SELECT

INSERT INTO ... SELECT

INSERT INTO ... SELECT

INSERT INTO ... SELECT with a bunch of

JOIN

JOIN

JOIN

JOINs

Cconqr ᯅ Are those statements supported though?

M

Matt Silverlock•9/24/23, 11:40 AM

Yes. INSERT / UPSERT … ON CONFLICT work.

C

conqr ᯅ•9/24/23, 1:40 PM

Is the LIMIT modifier not allowed on DELETE commands?

DELETE FROM offers WHERE price=5 LIMIT 1

near "LIMIT": syntax error

K

kian•9/24/23, 1:43 PM

correct

C

conqr ᯅ•9/24/23, 1:43 PM

Seems to not work on UPDATE commands too

UPDATE users SET balance = balance + 10 WHERE id = 'test' LIMIT 1

near "LIMIT": syntax error

K

kian•9/24/23, 1:43 PM

It's an optional feature in SQLite and isn't enabled in D1.

C

conqr ᯅ•9/24/23, 1:44 PM

It works for other commands though

K

kian•9/24/23, 1:44 PM

The feature is about UPDATE and DELETE statements.

K

kian•9/24/23, 1:44 PM

SQLITE_ENABLE_UPDATE_DELETE_LIMIT

SQLITE_ENABLE_UPDATE_DELETE_LIMIT

SQLITE_ENABLE_UPDATE_DELETE_LIMIT

SQLITE_ENABLE_UPDATE_DELETE_LIMIT

This option enables an optional ORDER BY and LIMIT clause on UPDATE and DELETE statements.

https://www.sqlite.org/compile.html

C

conqr ᯅ•9/24/23, 1:46 PM

C

captain•9/24/23, 3:33 PM

I'm noticing in the dasboard for d1 its only text, integer, real and blob when setting up a table. Does tha mean if I run something like:

CREATE TABLE IF NOT EXISTS messages (
  title text NOT NULL,
  body text NOT NULL,
  amount INTEGER NOT NULL,
  color VARCHAR(10) NOT NULL,
);

CREATE TABLE IF NOT EXISTS messages (
  title text NOT NULL,
  body text NOT NULL,
  amount INTEGER NOT NULL,
  color VARCHAR(10) NOT NULL,
);

CREATE TABLE IF NOT EXISTS messages (
  title text NOT NULL,
  body text NOT NULL,
  amount INTEGER NOT NULL,
  color VARCHAR(10) NOT NULL,
);

CREATE TABLE IF NOT EXISTS messages (
  title text NOT NULL,
  body text NOT NULL,
  amount INTEGER NOT NULL,
  color VARCHAR(10) NOT NULL,
);

That the VARCHAR(10) is really just text and I don't need to state VARCHAR(10) because there will be no performance or size settings by setting that limitation behind the scenes?

Original message was deleted

C

captain•9/24/23, 3:42 PM

got it, so so I don't need to waste time worrying about varchar(10) i can set it to text. Follow up question, an epoch timestamp is bigger than an integer, should sometime saving that info be saved as text or what do you recommend for setting timestamps on entries?

Original message was deleted

C

captain•9/24/23, 3:45 PM

for instance in this thread I see somebody setting: time_stamp timestamp NOT NULL DEFAULT,

C

captain•9/24/23, 3:45 PM

how is that converted?

Original message was deleted

C

captain•9/24/23, 3:47 PM

for instance in my scenario, i have different customer ids, and I'm tracking specific log actions via their id and the time it happened. then someday i might want to go back and query the last week of action organized in newest to old, or go back to 2 months ago for only a range of a month. What would be the best way of storing that timestamp?

C

captain•9/24/23, 3:48 PM

currently i'm saving the epoch time in my key of my KV entry

C

captain•9/24/23, 3:48 PM

but listing keys and doing that sort isn't really possible

C

captain•9/24/23, 3:49 PM

got it

C

captain•9/24/23, 3:53 PM

so an epoch time generated via worker would be 1695071510081, but that is bigger than an INT, and BIGINT would probably get converted to REAL, so better to just set that value to REAL, correct?

C

captain•9/24/23, 3:53 PM

but behind the scenes does any of this matter, and could it just be stored as TEXT?

C

captain•9/24/23, 3:55 PM

or nevermind, best to do it as an integer

C

captain•9/24/23, 3:55 PM

okay well thank LEO, appreciate your time

Original message was deleted

C

captain•9/24/23, 4:01 PM

thanks Leo, appreciate your time

C

captain•9/24/23, 4:36 PM

Hello, wondering if anybody can see why this wont run?
sudo wrangler d1 execute mydevdatabase --file schemas/schema.sql

DROP TABLE IF EXISTS messages;
CREATE TABLE IF NOT EXISTS messages (
  title TEXT NOT NULL,
  body TEXT NOT NULL,
  amount INTEGER NOT NULL,
  color TEXT NOT NULL,
  event_type TEXT NOT NULL,
  e_id TEXT NOT NULL, 
  i_id TEXT NOT NULL, -- invoice id
  o_id TEXT NOT NULL, --
  s_id TEXT NOT NULL, -- subscription id
  p_id TEXT NOT NULL, -- payment id
  c_id TEXT NOT NULL, -- customer id
  service TEXT NOT NULL, 
  email TEXT NOT NULL,
  name TEXT NOT NULL,
  link TEXT NOT NULL,
  related_locations TEXT NOT NULL,
  time_stamp INTEGER NOT NULL DEFAULT,
  customer_dismiss INTEGER, -- 0 or 1
  location_id TEXT NOT NULL,
  status TEXT NOT NULL, -- new or dismissed
  status_type TEXT NOT NULL, -- notification / 
  other TEXT NOT NULL
);

DROP TABLE IF EXISTS messages;
CREATE TABLE IF NOT EXISTS messages (
  title TEXT NOT NULL,
  body TEXT NOT NULL,
  amount INTEGER NOT NULL,
  color TEXT NOT NULL,
  event_type TEXT NOT NULL,
  e_id TEXT NOT NULL, 
  i_id TEXT NOT NULL, -- invoice id
  o_id TEXT NOT NULL, --
  s_id TEXT NOT NULL, -- subscription id
  p_id TEXT NOT NULL, -- payment id
  c_id TEXT NOT NULL, -- customer id
  service TEXT NOT NULL, 
  email TEXT NOT NULL,
  name TEXT NOT NULL,
  link TEXT NOT NULL,
  related_locations TEXT NOT NULL,
  time_stamp INTEGER NOT NULL DEFAULT,
  customer_dismiss INTEGER, -- 0 or 1
  location_id TEXT NOT NULL,
  status TEXT NOT NULL, -- new or dismissed
  status_type TEXT NOT NULL, -- notification / 
  other TEXT NOT NULL
);

DROP TABLE IF EXISTS messages;
CREATE TABLE IF NOT EXISTS messages (
  title TEXT NOT NULL,
  body TEXT NOT NULL,
  amount INTEGER NOT NULL,
  color TEXT NOT NULL,
  event_type TEXT NOT NULL,
  e_id TEXT NOT NULL, 
  i_id TEXT NOT NULL, -- invoice id
  o_id TEXT NOT NULL, --
  s_id TEXT NOT NULL, -- subscription id
  p_id TEXT NOT NULL, -- payment id
  c_id TEXT NOT NULL, -- customer id
  service TEXT NOT NULL, 
  email TEXT NOT NULL,
  name TEXT NOT NULL,
  link TEXT NOT NULL,
  related_locations TEXT NOT NULL,
  time_stamp INTEGER NOT NULL DEFAULT,
  customer_dismiss INTEGER, -- 0 or 1
  location_id TEXT NOT NULL,
  status TEXT NOT NULL, -- new or dismissed
  status_type TEXT NOT NULL, -- notification / 
  other TEXT NOT NULL
);

DROP TABLE IF EXISTS messages;
CREATE TABLE IF NOT EXISTS messages (
  title TEXT NOT NULL,
  body TEXT NOT NULL,
  amount INTEGER NOT NULL,
  color TEXT NOT NULL,
  event_type TEXT NOT NULL,
  e_id TEXT NOT NULL, 
  i_id TEXT NOT NULL, -- invoice id
  o_id TEXT NOT NULL, --
  s_id TEXT NOT NULL, -- subscription id
  p_id TEXT NOT NULL, -- payment id
  c_id TEXT NOT NULL, -- customer id
  service TEXT NOT NULL, 
  email TEXT NOT NULL,
  name TEXT NOT NULL,
  link TEXT NOT NULL,
  related_locations TEXT NOT NULL,
  time_stamp INTEGER NOT NULL DEFAULT,
  customer_dismiss INTEGER, -- 0 or 1
  location_id TEXT NOT NULL,
  status TEXT NOT NULL, -- new or dismissed
  status_type TEXT NOT NULL, -- notification / 
  other TEXT NOT NULL
);

however getting this error:

  ERROR 9009: SQL prepare error: near ",": syntax error in CREATE TABLE IF NOT EXISTS messages (
    title TEXT NOT NULL,
    body TEXT NOT NULL,
    amount INTEGER NOT NULL,
    color TEXT NOT NULL,
    event_type TEXT NOT NULL,
    e_id TEXT NOT NULL,
    i_id TEXT NOT NULL, -- invoice id
    o_id TEXT NOT NULL, --
    s_id TEXT NOT NULL, -- subscription id
    p_id TEXT NOT NULL, -- payment id
    c_id TEXT NOT NULL, -- customer id
    service TEXT NOT NULL,
    email TEXT NOT NULL,
    name TEXT NOT NULL,
    link TEXT NOT NULL,
    related_locations TEXT NOT NULL,
    time_stamp INTEGER NOT NULL DEFAULT,
    customer_dismiss INTEGER,
    location_id TEXT NOT NULL,
    status TEXT NOT NULL, -- new or dismissed
    status_type TEXT NOT NULL, -- notification /
    other TEXT NOT NULL
  ); at offset 524 [code: 7500]

  ERROR 9009: SQL prepare error: near ",": syntax error in CREATE TABLE IF NOT EXISTS messages (
    title TEXT NOT NULL,
    body TEXT NOT NULL,
    amount INTEGER NOT NULL,
    color TEXT NOT NULL,
    event_type TEXT NOT NULL,
    e_id TEXT NOT NULL,
    i_id TEXT NOT NULL, -- invoice id
    o_id TEXT NOT NULL, --
    s_id TEXT NOT NULL, -- subscription id
    p_id TEXT NOT NULL, -- payment id
    c_id TEXT NOT NULL, -- customer id
    service TEXT NOT NULL,
    email TEXT NOT NULL,
    name TEXT NOT NULL,
    link TEXT NOT NULL,
    related_locations TEXT NOT NULL,
    time_stamp INTEGER NOT NULL DEFAULT,
    customer_dismiss INTEGER,
    location_id TEXT NOT NULL,
    status TEXT NOT NULL, -- new or dismissed
    status_type TEXT NOT NULL, -- notification /
    other TEXT NOT NULL
  ); at offset 524 [code: 7500]

  ERROR 9009: SQL prepare error: near ",": syntax error in CREATE TABLE IF NOT EXISTS messages (
    title TEXT NOT NULL,
    body TEXT NOT NULL,
    amount INTEGER NOT NULL,
    color TEXT NOT NULL,
    event_type TEXT NOT NULL,
    e_id TEXT NOT NULL,
    i_id TEXT NOT NULL, -- invoice id
    o_id TEXT NOT NULL, --
    s_id TEXT NOT NULL, -- subscription id
    p_id TEXT NOT NULL, -- payment id
    c_id TEXT NOT NULL, -- customer id
    service TEXT NOT NULL,
    email TEXT NOT NULL,
    name TEXT NOT NULL,
    link TEXT NOT NULL,
    related_locations TEXT NOT NULL,
    time_stamp INTEGER NOT NULL DEFAULT,
    customer_dismiss INTEGER,
    location_id TEXT NOT NULL,
    status TEXT NOT NULL, -- new or dismissed
    status_type TEXT NOT NULL, -- notification /
    other TEXT NOT NULL
  ); at offset 524 [code: 7500]

  ERROR 9009: SQL prepare error: near ",": syntax error in CREATE TABLE IF NOT EXISTS messages (
    title TEXT NOT NULL,
    body TEXT NOT NULL,
    amount INTEGER NOT NULL,
    color TEXT NOT NULL,
    event_type TEXT NOT NULL,
    e_id TEXT NOT NULL,
    i_id TEXT NOT NULL, -- invoice id
    o_id TEXT NOT NULL, --
    s_id TEXT NOT NULL, -- subscription id
    p_id TEXT NOT NULL, -- payment id
    c_id TEXT NOT NULL, -- customer id
    service TEXT NOT NULL,
    email TEXT NOT NULL,
    name TEXT NOT NULL,
    link TEXT NOT NULL,
    related_locations TEXT NOT NULL,
    time_stamp INTEGER NOT NULL DEFAULT,
    customer_dismiss INTEGER,
    location_id TEXT NOT NULL,
    status TEXT NOT NULL, -- new or dismissed
    status_type TEXT NOT NULL, -- notification /
    other TEXT NOT NULL
  ); at offset 524 [code: 7500]

I

Isaac McFadyen•9/24/23, 4:38 PM

You forgot a default on time_stamp

I

Isaac McFadyen•9/24/23, 4:39 PM

time_stamp INTEGER NOT NULL DEFAULT,

There's no value for DEFAULT. It should be

time_stamp INTEGER NOT NULL DEFAULT CURRENT_TIMESTAMP,

I

Isaac McFadyen•9/24/23, 4:39 PM

See section 3.2 here: https://www.sqlite.org/lang_createtable.html

As pointed out above it’s an alpha product and you should not be using it for production. But haven’

Similar Threads

Similar Threads

Similar Threads