@Cloudflare (Dev) why there is no rename option for files in my r2 buckets? any specific reasons, I

VVijay @Cloudflare (Dev) why there is no rename option for files in my r2 buckets? any ...

H

Hello, I’m Allie!•7/13/24, 9:01 AM

Try #r2

RRahul For example, using a Firebase function, when new user data is saved in Firebase ...

I

Isaac McFadyen•7/13/24, 3:59 PM

So I think they're suggesting that you just call your API endpoint when creating a new user.

I

Isaac McFadyen•7/13/24, 3:59 PM

In your example, rather than creating user in the Function -> firebase calls your endpoint, you just create user and then call your endpoint from the same Function.

ZZiga Zajc Any estimates on when the feature to dynamically create multiple databases would...

H

Hello, I’m Allie!•7/13/24, 7:11 PM

:soontm:

MMax (@rozenmd)good idea, we'll add it

S

Sam•7/13/24, 7:47 PM

Also — and sorry for mentioning you, it would also be really cool if we could add descriptions to the D1’s. So team members can see what the D1 is exactly for.

Same for R2, queue’s and a single Worker.

森森@VerseLink (RW)Is there a roadmap of when we can get to Sessions API for D1? As in could we exp...

M

murzin•7/13/24, 8:44 PM

Any updates on this? Would be insanely dope to have replicas for D1

M

murzin•7/13/24, 8:46 PM

Also if you need any alpha testers, all for it

ZZiga Zajc also based on Slovenian law, everything needs to be stored for at least 10 years

H

Hello, I’m Allie!•7/14/24, 8:36 AM

Another thing too is that while the law may require storing data for 10 years, it may only be actively used for a shorter period of time. Any data that is older than that could be pushed as a compressed dump to R2, for example

H

Hello, I’m Allie!•7/14/24, 8:37 AM

It’s still there, and can still be recalled, but it won’t count toward the 10 GB limit

W

wataru•7/14/24, 7:12 PM

Hello. I have a question. How would you connect a local Cloudflare D1 DB through a script?

This is

exec.ts

exec.ts

exec.ts

exec.ts, I will want to use this script for seeding against my local environment.

import { Log, LogLevel, Miniflare } from "miniflare";

const nullScript =
  "export default {fetch: () => new Response(null, {status:404})};";
const mf = new Miniflare({
  modules: true,
  script: nullScript,
  d1Databases: { DB: "xxx-xxx" },
  log: new Log(LogLevel.INFO),
});

const env = await mf.getBindings();
const { results } = await (env.DB as D1Database)
  .prepare(`PRAGMA table_list;`)
  .all();
console.log(results);
await mf.dispose();

import { Log, LogLevel, Miniflare } from "miniflare";

const nullScript =
  "export default {fetch: () => new Response(null, {status:404})};";
const mf = new Miniflare({
  modules: true,
  script: nullScript,
  d1Databases: { DB: "xxx-xxx" },
  log: new Log(LogLevel.INFO),
});

const env = await mf.getBindings();
const { results } = await (env.DB as D1Database)
  .prepare(`PRAGMA table_list;`)
  .all();
console.log(results);
await mf.dispose();

import { Log, LogLevel, Miniflare } from "miniflare";

const nullScript =
  "export default {fetch: () => new Response(null, {status:404})};";
const mf = new Miniflare({
  modules: true,
  script: nullScript,
  d1Databases: { DB: "xxx-xxx" },
  log: new Log(LogLevel.INFO),
});

const env = await mf.getBindings();
const { results } = await (env.DB as D1Database)
  .prepare(`PRAGMA table_list;`)
  .all();
console.log(results);
await mf.dispose();

import { Log, LogLevel, Miniflare } from "miniflare";

const nullScript =
  "export default {fetch: () => new Response(null, {status:404})};";
const mf = new Miniflare({
  modules: true,
  script: nullScript,
  d1Databases: { DB: "xxx-xxx" },
  log: new Log(LogLevel.INFO),
});

const env = await mf.getBindings();
const { results } = await (env.DB as D1Database)
  .prepare(`PRAGMA table_list;`)
  .all();
console.log(results);
await mf.dispose();

Then, I'm executing this with

npx tsx exec.ts

npx tsx exec.ts

npx tsx exec.ts

npx tsx exec.ts

The app’s D1 has a “users” table that I created through the

wrangler d1 execute

wrangler d1 execute

command. The Miniflare in the

exec.ts

exec.ts

exec.ts

exec.ts doesn't acknowledge the “users” table.

I have only one D1 Database, and can confirm that the

.wrangler/state/v3/d1/miniflare-D1DatabaseObject

.wrangler/state/v3/d1/miniflare-D1DatabaseObject

.wrangler/state/v3/d1/miniflare-D1DatabaseObject

.wrangler/state/v3/d1/miniflare-D1DatabaseObject has only one set of files.

Your help is appreciated!

B

bennycondon•7/15/24, 3:27 AM

Hey there! This might be more of an SQLite question than a D1 quetion. But, is there a way to treat NULLs as indistinct in SQLite? I found this, which explains there is NULL_ALWAYS_DISTINCT to always treat NULLs as distinct. But, I haven't found a way to always treat NULLs as indistinct? I'd like to to perform INSERT OR IGNORE queries using ON CONFLICT and a UNIQUE CONSTRAINT that may include NULLs.

布

布鲁诺普雷托•7/15/24, 2:07 PM

CREATE TABLE Players (
  player_id INT PRIMARY KEY,
  player_name VARCHAR(50) NOT NULL,
  server_id INT,
  FOREIGN KEY (server_id) REFERENCES Servers(server_id)
);

CREATE TABLE Players (
  player_id INT PRIMARY KEY,
  player_name VARCHAR(50) NOT NULL,
  server_id INT,
  FOREIGN KEY (server_id) REFERENCES Servers(server_id)
);

CREATE TABLE Players (
  player_id INT PRIMARY KEY,
  player_name VARCHAR(50) NOT NULL,
  server_id INT,
  FOREIGN KEY (server_id) REFERENCES Servers(server_id)
);

CREATE TABLE Players (
  player_id INT PRIMARY KEY,
  player_name VARCHAR(50) NOT NULL,
  server_id INT,
  FOREIGN KEY (server_id) REFERENCES Servers(server_id)
);

Does D1 support this as well as junction tables

布布鲁诺普雷托 ```sql CREATE TABLE Players ( player_id INT PRIMARY KEY, player_name VARCHAR...

M

Matt Silverlock•7/15/24, 7:22 PM

Foreign keys? Yes. https://developers.cloudflare.com/d1/build-with-d1/foreign-keys/

Cloudflare Docs

Define foreign keys · Cloudflare D1 docs

D1 supports defining and enforcing foreign key constraints across tables in a database.