LOkey 
LIt is healthier to write your codes with wrangler instead of using quick edit.
LCan you send a remote link pm.
Hyup
HFixed, I'm a literal idiot
MBetter: a locally isolated version - https://developers.cloudflare.com/d1/learning/local-development/
D1 has fully-featured support for local development, running the same version of D1 as Cloudflare runs globally. Local development uses Wrangler, the …
LHello again @elithrar
I am sharing a part of the code I wrote.facing an error, how can I fix it.Thanks in advance..
Error Response:
The 'length' property is not of type 'D1Result<unknown>'.
I am sharing a part of the code I wrote.facing an error, how can I fix it.Thanks in advance..
Error Response:
The 'length' property is not of type 'D1Result<unknown>'.
Kall()you probably want it to be
const { results } = await stmt.all();resultswhich is an array of returned rows
Lconst { results } = await stmt.all();Thanks for the help.
How can I query whether the result value is empty or not
Kresultsnull
KTake a look at this
LOki, I'll look.
LThe solution: @kiannh thx
SI have a billing question. If I have a table full of indexed images and I want to read one I know the index of how many read units would that use? Would it have to scan the whole table? Or would knowing the index just make it one read unit with the right query?
MOne for the index and one for the table row, as a generalization / not committal.
YHave a 100k line SQL import I want to do.
Gets hung up on "Mapping SQL input into an array of statements"
Read that splitting into files with 5k lines helps.
Any tools to do this or should I just manually go through it?
Gets hung up on "Mapping SQL input into an array of statements"
Read that splitting into files with 5k lines helps.
Any tools to do this or should I just manually go through it?
SFrom my understanding that doesn't make sense. Aren't the read units based on how many 4 kB chunks you use when searching. So if the image is under 4 kilobytes including the index it should be one read if it doesn't have to scan the rest of the table right.
MReading an index will likely always be an additional operation (read unit). We will make this clearer in the docs as we refine our pricing.
SCool
SIs there a way I can test how a lookup would be counted during this time?
MNot yet, per the docs: https://developers.cloudflare.com/d1/platform/pricing/
- we are working on it. Won’t be within the next month. Focusing on Time Travel and stability.
While in public Alpha, D1 is currently free to use on all Workers plans. Refer to the our recent announcement) for more information.
MKeep in mind that you would need to serve 25 billion requests with that query pattern to exhaust the 50B included read units. 25B / 30 / 86400 = 9600+ requests/sec, 24/7/30.
MI did it manually, but if you do find a good secure tool to use, hit me up
MWe're planning on removing the "Mapping SQL input into an array of statements" step from wrangler fwiw
MMerged the PR + cleaned up migrations output a bit
MD1's experimental backend runs your SQL within a transaction automatically fwiw
Moh nah I mean when you run
npx wrangler d1 executenpx wrangler d1 migrations apply- the SQL executes within a transaction
MWe’re looking at alternatives that make it easier to interleave SQL and JS. We can’t give you a specific timeline. The blog highlights what we are focusing on in the near term for D1.
Mi think we borrowed that from the cf v4 api
MAnyone else getting this when trying to use the experimental backend for new D1 databases?
not authorized to use function: strftimeMWorks locally and worked with old DBs. Tried to create a copy of my DB with the experimental backend and I'm now getting this error.
Mcan you file an issue against workerd? https://github.com/cloudflare/workerd/issues
we're gradually allow-listing functions and may have missed a few
we're gradually allow-listing functions and may have missed a few
MWill do that right now!
MAny expectation on how long that'll take to make it in? Curious if I should roll back to my old DB and write batching functions instead (which is why I was trying a move to the new backend).
