Any idea why `wrangler d1 execute EmailTracker --command='SELECT * FROM SenderInfo WHERE email = "dr

Any idea why

wrangler d1 execute EmailTracker --command='SELECT * FROM SenderInfo WHERE email = "drnewt536@gmail.com";'

wrangler d1 execute EmailTracker --command='SELECT * FROM SenderInfo WHERE email = "drnewt536@gmail.com";'

wrangler d1 execute EmailTracker --command='SELECT * FROM SenderInfo WHERE email = "drnewt536@gmail.com";'

wrangler d1 execute EmailTracker --command='SELECT * FROM SenderInfo WHERE email = "drnewt536@gmail.com";' fails, yet

wrangler d1 execute EmailTracker --command="SELECT * FROM SenderInfo WHERE email = 'drnewt536@gmail.com';"

wrangler d1 execute EmailTracker --command="SELECT * FROM SenderInfo WHERE email = 'drnewt536@gmail.com';"

wrangler d1 execute EmailTracker --command="SELECT * FROM SenderInfo WHERE email = 'drnewt536@gmail.com';"

wrangler d1 execute EmailTracker --command="SELECT * FROM SenderInfo WHERE email = 'drnewt536@gmail.com';" passes

sokorototoOP•6/13/23, 12:21 PM

I just changed it from "--""--" to '--''--'

Ssokorototo Any idea why `wrangler d1 execute EmailTracker --command='SELECT * FROM SenderIn...

Max (@rozenmd)•6/13/23, 1:12 PM

"...""..." means column, or general database objects - you want '...''...' for strings

Ttjenkinson hi with the `batch` api is it possible to get the results of all statements up t...

Matt Silverlock•6/13/23, 7:53 PM

It is not. The batch runs in an implicit transaction, so that a batch doesn’t “partially” complete and leave your database in an unexpected state.

Ttjenkinson Thanks. Could it not still return the results from earlier stages though, even i...

Matt Silverlock•6/13/23, 7:58 PM

That’s not how a transaction works. What if some of those earlier queries insert data? Modify the schema? Or return nothing? etc.

If you need to treat them as discrete queries, issue multiple separate queries

Ttjenkinson I think it would still be helpful to see what the output was with the understand...

Matt Silverlock•6/13/23, 8:22 PM

We plan to expose a transaction API, but you can’t do this right now

Adi•6/14/23, 1:33 AM

Some of the discussion actually reminded me of a question I have had since wrangler3/miniflare3 came out.
With those old miniflare packages (https://www.npmjs.com/package/@miniflare/d1) when in a test environment, you could write code that would simulate d1 in the following way

import { D1Database, D1DatabaseAPI } from "@miniflare/d1";
import { drizzle } from "drizzle-orm/d1";

const d1 = new D1Database(new D1DatabaseAPI(sqliteDb));
const db = drizzle(d1); // now I can can write unit tests for drizzle

import { D1Database, D1DatabaseAPI } from "@miniflare/d1";
import { drizzle } from "drizzle-orm/d1";

const d1 = new D1Database(new D1DatabaseAPI(sqliteDb));
const db = drizzle(d1); // now I can can write unit tests for drizzle

How can I write this with miniflare 3?

MMatt Silverlock Yes, but not > 100 at this stage. I’d like to get a better understanding of your...

Jason Hostetter•6/14/23, 2:53 AM

I ended up refactoring my query into two separate queries, which now seems to keep it under the depth of 20 limit. I initially had the queries combined with nested CTEs so that I could avoid two DB round-trips, but it seems like the speed of the new backend more than makes up for it. It's really fast now.

Matt Silverlock•6/14/23, 5:59 PM

Typically a week or two, but best to not look at commits to workerd. We'll publish in the changelog once it ships: https://developers.cloudflare.com/d1/changelog

Sameer Ali•6/14/23, 10:07 PM

deleting table with 1000 rows would count 1000 writes?

Matt Silverlock•6/15/23, 11:47 AM

Self-plug: built an authenticated HTTP API on top of D1 so you can query it from legacy/non-Workers apps: https://twitter.com/elithrar/status/1668601365860425733?s=46

Matt Silverlock 🐀 (@elithrar)

Built an example app that combines @Cloudflare D1 and @honojs to put an authenticated HTTP API in front of your database: https://t.co/6RVspFGe5V

Exposes .all(), .exec() and .batch() to any existing app:

Twitter

•

6/13/23, 12:49 PM

Murder Chicken•6/15/23, 3:03 PM

Is there a way to intentionally throw a proper D1 error that has an error.causeerror.cause attribute?

MMurder Chicken Is there a way to intentionally throw a proper D1 error that has an `error.cause...

Matt Silverlock•6/15/23, 3:14 PM

Catch and re-throw with error.cause.messageerror.cause.message

? https://developers.cloudflare.com/d1/platform/client-api/#errors

D1 client API · Cloudflare D1 docs

As part of our Client API, both static and prepared statements are supported. Best practice is to use prepared statements which are precompiled …

Murder Chicken•6/15/23, 3:15 PM

That's what I ended up doing

Murder Chicken•6/15/23, 3:16 PM

But what I was really interested in was if there was an easy way to trigger an error. Trying to test that the try/catch is working properly but didn't want to get hacky with the actual queries.

Murder Chicken•6/15/23, 3:18 PM

Never mind, I see an example in the docs! Thanks for the direction!

Hello, I’m Allie!•6/15/23, 3:43 PM

Is there a way to run()run() a batch? Like, execute the batch statements, but don’t return anything to the calling Worker?

HHello, I’m Allie!Is there a way to `run()` a batch? Like, execute the batch statements, but don’t...

Matt Silverlock•6/15/23, 3:57 PM

Like .exec().exec()

what are you trying to do? You can just… ignore the result. await db.batch(statements)await db.batch(statements)

meyer•6/15/23, 5:22 PM

smh i can’t post a dang drizzle discord invite link

meyer•6/15/23, 5:23 PM

well anyways there’s a drizzle discord

meyer•6/15/23, 5:23 PM

exZajY9H

MMatt Silverlock Like `.exec()` - what are you trying to do? You can just… ignore the result. `aw...

Hello, I’m Allie!•6/15/23, 5:48 PM

Isn’t that the point with run()run() itself? Like, if you have a statement where you don’t need the results at all, or loading the results into memory would be a waste, then you run()run() instead of first()first() or all()all(). And I would expect the size argument to be even more compelling if you are batching many statements together

Hello, I’m Allie!•6/15/23, 5:48 PM

So like, it’s not that you can’t just ignore the results

Hello, I’m Allie!•6/15/23, 5:49 PM

Just that it is more efficient to not have them sent in the first place

Any idea why `wrangler d1 execute EmailTracker --command='SELECT * FROM SenderInfo WHERE email = "dr

Similar Threads

Similar Threads

Similar Threads