How will workers figure out which D1 replica to read from? Something using the smart placement featu
How will workers figure out which D1 replica to read from? Something using the smart placement feature?
MWe'll share more once we get closer 
Msounds like you might want to debounce your searches every 300ms or so https://github.com/sindresorhus/debounce-fn
MIf you had 100,000 rows, each 200 bytes wide, and had to perform a full table scan every time - that’s approximately 5,000 read units out of the 25 billion per month included - or 5 million full table scans. Free.
MThis isn’t to say an index - https://developers.cloudflare.com/d1/learning/using-indexes/
- https://stackoverflow.com/a/57082926/556573
- isn’t useful, but unless you have millions of rows or really wide rows, cost isn’t likely to be a problem. Performance is the reason.
Indexes enable D1 to improve query performance over the indexed columns for common (popular) queries by reducing the amount of data (number of rows) …
Stack Overflow
There is sort order when creating index for sqlite.
https://sqlite.org/lang_createindex.html
Each column name or expression can be followed by one of the "ASC" or "DESC" keywords to indicate ...
https://sqlite.org/lang_createindex.html
Each column name or expression can be followed by one of the "ASC" or "DESC" keywords to indicate ...
MIndexes that optimize ORDER BY must consider the ASC/DESC and NULLS FIRST/LAST modifiers.
MI’d suggest following the D1 tutorial if you haven’t yet: https://developers.cloudflare.com/d1/get-started/
- this will show you how to query a D1 DB from a Worker.
NI remember seeing an intellij plugin for d1, but I can't find it anywhere, could somebody help me?
N
Mcc @geelen
MWhy indexes are useful (I was writing a little demo app w/ Remix...)
ORDER BY random() LIMIT 25-> 78ms query execution timeORDER BY created_at DESC LIMIT 25with an index oncreated_at DESC-> 0.20ms query execution time
JI just noticed a table called 
_cf_KV on every D1 database. This table has two columns, key and value. This has nothing to do with the actual KV product, has it? 
HThat might be prep for the SQL-on-DOs thing they are coming out with soon. According to Kenton(https://canary.discord.com/channels/595317990191398933/773219443911819284/1128025139632681131), regular DO KV storage will be stored in a SQLite Table, which might be what that is...
JThanks for the insights, that's very interesting and definitely good do know!
MNothing to do with KV the product
Mis there a size limit to what you can do with
db.batch() and/or db.exec()?
BIt appears
npx wrangler d1 migrations apply some-db --experimental-backend only works when logged in via npx wrangler login. In CI, however, where I'm not running npx wrangler login but instead providing a CLOUDFLARE_API_TOKEN env variable the command exits with code 1. Is this a known issue? What workarounds exist for running migrations in CI?B(I've confirmed I can run commands such as
npx wrangler pages deploy dist --project-name abc in CI only providing the CLOUDFLARE_API_TOKEN env var.)BYeah, also provided that. Unfortunately I don't see any additional output.
BSince it works locally with
wrangler login I assume this is probably just an auth bug? Is there any way to provide auth in CI besides using the env vars?Bi.e. could I somehow make
wrangler login work in CI?BGood question. I'll look into that. Thanks!
BThat was it!! Thanks @skye_31
BDidn't have D1 permissions on the token. Appreciate the help!
Myour wrangler.toml needs to have a
main entry pointing at your worker entrypoint, like main = "src/index.ts"MDid you create the DB on its own? Strongly suggest following the guide at least once: https://developers.cloudflare.com/d1/get-started/
Thad anyone setup serverless framework with D1?
MWhich specific framework? We have a ton of examples:
- D1 + Hono: https://developers.cloudflare.com/d1/tutorials/build-a-comments-api/
- Full stack framework code snippets: https://developers.cloudflare.com/d1/examples/
- Long list of framework guides: https://developers.cloudflare.com/pages/framework-guides/
TEasily develop and monitor auto-scaling applications on AWS Lambda, API Gateway, DynamoDB, etc., with the Serverless Framework and Serverless Monitoring Dashboard.
MMI don't think that serverless plugin supports wrangler 2, let alone D1 
Thmm serverless framework doesnt work much on any other cloud
Tseems it heavily favors AWS
MFYI — if you're using D1's new
--experimental-backend and want to try D1's new Time Travel feature — you now can. This is a work-in-progress but sharing here. This preview branch may break at any time.- You can now use a temporary wrangler branch
npx wrangler@d1 d1 time-travel restore DB_NAME --timestamp=(unix timestamp|RFC3339 timestamp)to restore a database to any minute within the last 30 days. - Our preview documentation is at https://silverlock-d1-time-travel.cloudflare-docs-7ou.pages.dev/d1/learning/time-travel/#docs-content
- For the initial release,
d1 time-travel restore DB_NAMEoverwrites your existing database (with confirmation). In the future, we'll allow you to fork and/or clone to a new DB or over the top of an existing database. - You can read more about Time Travel from our original announcement post back in May: https://blog.cloudflare.com/d1-turning-it-up-to-11/#time-travel
MPer the docs, yes: Time Travel will be the default. We address durability by writing databases to cold (object) storage: this is where idle databases are restored from.
Way too early to comment on anything non-JSON. Unlikely to be Protobuf.
Way too early to comment on anything non-JSON. Unlikely to be Protobuf.
H
SIf I already created a D1 database on the dashboard, how can I interact with it during local development?
Smy wrangler.toml is this:
although when doing wrangler pages dev, it's undefined
although when doing wrangler pages dev, it's undefined
Shonestly I'm just completely lost 
