Hello, thanks for reporting this. I've just pushed a new release for `cf-bindings-proxy` (v0.5.0) to

Hello, thanks for reporting this. I've just pushed a new release for

cf-bindings-proxy

cf-bindings-proxy

(v0.5.0) to fix this bug.

JJames Hello, thanks for reporting this. I've just pushed a new release for `cf-binding...

Donnager•9/1/23, 5:42 PM

oh awesome!! thank you for letting me know sir!

Original message was deleted

Matt Silverlock•9/1/23, 8:33 PM

No, but setting an automatic

expires_at

expires_at

column and using that in your queries (and indexes) can get you there. You can do a cleanup with another trigger or a Cron Trigger Worker that runs periodically and separately cleans up

WHERE expires_at < now()

WHERE expires_at < now()

Original message was deleted

Matt Silverlock•9/1/23, 8:34 PM

FWIW, Postgres / MySQL don't do this without custom extensions, and the approach is the same. You could also use a view that elides "expired" rows and query that.

Original message was deleted

Matt Silverlock•9/1/23, 8:35 PM

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

0xidigwu•9/3/23, 1:07 AM

Hello, I currently trying out d1 with worker-rs but for some reason, i cant query the database from the worker, it keeps throwing

SqliteError: no such table: my-table

SqliteError: no such table: my-table

0xidigwu•9/3/23, 1:09 AM

heres the code

#[derive(Deserialize, Serialize, Debug)]
struct Thing {
    thing_id: String,
    desc: String,
    num: u32,
}

#[event(fetch, respond_with_errors)]
async fn main(req: Request, env: Env, _ctx: Context) -> Result<Response> {
    Router::new()
        .get_async("/:id", |_, ctx| async move {
            let id = ctx.param("id").unwrap();
            let d1 = ctx.env.d1("DB")?;

            let statement = d1.prepare("SELECT * FROM todos WHERE id = ?");
            let query = statement.bind(&[id.into()])?;

            let result = query.first::<Thing>(None).await?;

            match result {
                Some(thing) => Response::from_json(&thing),
                None => Response::error("Not found", 404),
            }
        })
        .run(req, env)
        .await
}

#[derive(Deserialize, Serialize, Debug)]
struct Thing {
    thing_id: String,
    desc: String,
    num: u32,
}

#[event(fetch, respond_with_errors)]
async fn main(req: Request, env: Env, _ctx: Context) -> Result<Response> {
    Router::new()
        .get_async("/:id", |_, ctx| async move {
            let id = ctx.param("id").unwrap();
            let d1 = ctx.env.d1("DB")?;

            let statement = d1.prepare("SELECT * FROM todos WHERE id = ?");
            let query = statement.bind(&[id.into()])?;

            let result = query.first::<Thing>(None).await?;

            match result {
                Some(thing) => Response::from_json(&thing),
                None => Response::error("Not found", 404),
            }
        })
        .run(req, env)
        .await
}

00xidigwu heres the code ``` #[derive(Deserialize, Serialize, Debug)] struct Thing { ...

Matt Silverlock•9/3/23, 1:14 PM

You code here doesn’t reference a

my-table

my-table

table at all. Is this definitely the code you’re running?

Ddpeek @geelen existing databases seem to be unaffected, so maybe there's just an issue...

jared•9/4/23, 6:09 AM

our existing databases are affected except the legacy alpha databases

Ggeelen but it was a small code change I made so easy fix, apologies for the interruptio...

Adi•9/4/23, 6:26 AM

Out of curiosity are these fixes pushed to workerd or wrangler-sdk (the public github repos). Or is it an internal repo that we can't see.
Asking cuz I had the sudden urge to see what the fix was

Adi•9/4/23, 6:29 AM

ooh I see

Matthijs•9/4/23, 8:04 AM

Hello, we are currently building out multiple prototypes with workers (TS) and D1 and I'm wondering if there is a recommended strategy when it comes to creating databases.
Currently we are creating a D1 database per worker so that one worker repo is in charge of the D1 instance and it's migrations. A worker in our stack has only one domain purpose and will expose only endpoints related to that domain.
But we are running into the 10 database limit, and we are wondering if we should consolidate D1 instances, any tips or best practices here?

Mmizchi Perhaps d1 is trying to split the line with ; before stripping the comment, and ...

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

It’s all here: https://github.com/cloudflare/workers-sdk/blob/e4bb5f36a947c0353c821ceee8279d970e3fde50/packages/wrangler/src/d1/execute.tsx#L334

GitHub

workers-sdk/packages/wrangler/src/d1/execute.tsx at e4bb5f36a947c03...

Home to Wrangler, the CLI for Cloudflare Workers® - cloudflare/workers-sdk

workers-sdk/packages/wrangler/src/d1/execute.tsx at e4bb5f36a947c03...

MMatt Silverlock You code here doesn’t reference a `my-table` table at all. Is this definitely th...

0xidigwu•9/4/23, 2:29 PM

apologies, the error was actually

SqliteError: no such table: todos

SqliteError: no such table: todos

00xidigwu apologies, the error was actually `SqliteError: no such table: todos`

itsmatteomanf•9/4/23, 5:45 PM

That looks like the table isn’t there, which I’m gonna believe. Can you check in the dashboard’s list of tables if the table exists?

Ssumé ሱሜ I have a table that gets periodicall updates (additions) in the form of a csv fi...

Matt Silverlock•9/5/23, 2:59 AM

Write a Worker that consumes the CSV and writes directly to D1?

Ssumé ሱሜ I was trying to make use of sqlite's ability to convert the csv into sql for me

Matt Silverlock•9/5/23, 3:39 AM

That’s less “SQLite” the query engine (what D1 uses) and more “SQLite the CLI tool” - they are different.

VViper Is there a working tutorial on how to connect to D1 using a Nextjs app?

Matt Silverlock•9/5/23, 11:15 AM

https://developers.cloudflare.com/pages/framework-guides/deploy-a-nextjs-site/#use-bindings-in-your-nextjs-application - replace KV with D1.

Deploy a Next.js site · Cloudflare Pages docs

Next.js is an open-source React framework for creating websites and applications. In this guide, you will create a new Next.js application and deploy …

addison•9/6/23, 3:53 AM

Is there a plan to have nicer errors. I cant find a better way to handle this error other than this and its kinda icky.

Unsmart•9/6/23, 4:17 AM

Not sure what you would want? Any way they format the errors you are going to have to do all the same conditions

Mehanika•9/6/23, 8:46 AM

Hello all. I am taking a deep look into D1. Is there any roadmap for when it will leave Alpha etc? Just to have an indication of the product maturity?

MMatt Silverlock There’s no practical limit on columns or rows (especially rows). We allow 100 co...

muslax•9/6/23, 8:51 AM

Is this new (100 cols per table)? Previously I managed to create a table with 269 cols, but now it always fails remotely (--local is still OK).

muslax•9/6/23, 8:52 AM

muslax•9/6/23, 8:56 AM

Codename_404•9/6/23, 9:46 AM

Is there plan to make d1 accessible externally as well? Or will it always be restricted to worker only?

Nehal Ali•9/6/23, 12:28 PM

i am getting an error "env.DB.prepare(...).run is not a function" , i logged env.DB and it is undefined,
in my controller i use it like this:

What did i do wrong here ?

#[derive(Deserialize, Serialize, Debug)] struct Thing { thing_id: String, desc: String, num: u32, } #[event(fetch, respond_with_errors)] async fn main(req: Request, env: Env, _ctx: Context) -> Result<Response> { Router::new() .get_async("/:id", |_, ctx| async move { let id = ctx.param("id").unwrap(); let d1 = ctx.env.d1("DB")?; let statement = d1.prepare("SELECT * FROM todos WHERE id = ?"); let query = statement.bind(&[id.into()])?; let result = query.first::<Thing>(None).await?; match result { Some(thing) => Response::from_json(&thing), None => Response::error("Not found", 404), } }) .run(req, env) .await }

Hello, thanks for reporting this. I've just pushed a new release for `cf-bindings-proxy` (v0.5.0) to

Similar Threads

Similar Threads

Similar Threads