the loose emoji on line 10 is probably the problem?
the loose emoji on line 10 is probably the problem?
Lit isnt an emoji, it's from copilot
Lit goes away if i tap aywhere else
Ti see
Lthats right
ICheck your line endings?
IThe "near ??" error makes it seem like there are some unprintable characters in there somewhere, maybe line endings or empty spaces?
MRuns perfectly for me as copied from @Max (@rozenmd)'s code block:
IIf you're on a Windows system try changing from CRLF to just LF?
MSomething is definitely off with your editor here, @Lucho.
The migration (just copy pasted from the docs):
The migration (just copy pasted from the docs):
Kat offset 0 is weird
Kit's pulled from
sqlite3_error_offsetJust tried CRLF vs LF and both work so that's not the issue.
KUsually if it's LF/CRLF you get a "you can't execute multiple statements" error or something like that
KA prepared SQL statement must contain only one statement. even
Lit might be
Li'll try doing the entire guide again from scratch
Ais d1 sqlite or sql? is sqlite worse?
Ait seems like sqlite is worse for anything potentially large scale from what im reading
MIs it possible to run a Prisma seed script and apply it to a D1 DB, either locally or remote? It would involve executing a TypeScript file i.e
seed.ts
MD1/sqlite fits some use cases, classic DBs fit others - depends what you're trying to do.
Asocial media application similar to letterboxd, bad idea or no? im between using D1 because im already using R2 + Pages for hosting or just using Planetscale
MPlanetscale would support scaling and replication from the start, D1 is still building it
MNo but cool idea - best is probably logging the prepared query string
wrangler d1 insightsregardless of that technically speaking, SQLite would be worse?
Mthere's no better/worse here, It Depends
Aon?
Mquery execution time inside D1, yeah
Mexpected reads/writes per second and amount of data stored to start with - sqlite can be really good for scaling simple read-heavy use cases really far as there's less to worry about
Mwhereas the tech underneath planetscale powers youtube, but you pay a price for that scalability
Athanks for the run down
Ais there a simple reason why CF chose SQLite then since mySQL seems superior
Msimple reason? easiest, most battle-tested path to enable an sql interface for storing data for Workers
Agot it
Aill just stick with keeping everything under cloudflare for now then and down the line when i do need "more" if CF isnt enough ill look into Planetscale
Aim reading the docs to query D1 locally with bindings, but im using next-pages and so when i develop locally i just use npm run dev for fast refresh, how am i supposed to initialize the prisma client in that case?
Athis is what i was using before for planetscale but obviously no database_url for d1
TIt's hard to maintain a large mysql cluster for the edge. Even if they do, the price will be as high as everest
TIn my case, D1, KV and R2 is perfectly fit. Most of the time my request are pagination, filtering with some predefined selected columns and get by ID. In mysql I will need a DB proxy to reduce the connections created and cache requests. With D1, it's not really faster but it's much cheaper without the worrying of connection managing and query caching.
Tyeah there are no dynamic binding yet
Tbut having a 50k warming database at the same time is mindblown
MLooks like we still need to manually configure database IDs in a global wrangler file as there’s no programmatic way to manage a fleet of D1 instancesYeah, dynamic bindings hasn't shipped yet, there's an unofficial package to automate the HTTP API steps you'd need to do atm though https://github.com/nora-soderlund/cloudflare-dynamic-bindings
Mwhat does D1 per DO mean
HSQLite Storage Bindings for DOs?
Mnot sure, unrelated work
MYou aren't going to get D1's in DO though, you'd get a raw sqlite instance
HWould the SQLite instance support replication?
HThat would be metal...
