because the client consuming the api is C#, and the datetime deserializer wants iso8601-1:2019
because the client consuming the api is C#, and the datetime deserializer wants iso8601-1:2019
DThis does mean that there is an intermediary cloudflare worker used to route the request. Maybe try to standardize it there?
Ask gippity what it knows about ISO 8601 standardization in sqlite, it might give you garbage but garbage is treasure to the right person
Ask gippity what it knows about ISO 8601 standardization in sqlite, it might give you garbage but garbage is treasure to the right person
UThis does mean that there is an intermediary cloudflare worker used to route the request. Maybe try to standardize it there?yeah that is pmuch what I'm trying to do right now
Useems like I could potentially do it on the JS side
U
Ujust gotta tell it that that's zulu time
Dyeah i'd much rather do it while its being routed in JS to reduce redundancy.
Dalso is that a CMD theme or did you take a picture with your iphone 3G and crop it?
Uhmm I wonder whether I could format it in the sql statement directly
Uthat's a terminal theme xD
Dcould you show it to me please
U
DI say its not worth the effort to search. The answer is right there with half a line of JS code and makes things much simpler at least for me
U(one sec for the theme settings)
Dthis is windows 11? 
Uwin10
Ubut using the windows terminal app
Uprofile settings:
color scheme:
color scheme:
Uyeah I suppose.
means I gotta post process a bunch of endpoints tho..
means I gotta post process a bunch of endpoints tho..
Uthen again I'm doing that anyway because I have to parse some json
Dits the easiest way I can think of
Dbut ask gippity
Unah this is fine
Dit might give you some golden garbage
Unice and simple
Dnice
SCan we add custom extensions to D1?
KKIt would likely follow the proposal of transactions being JavaScript, in the form of a Worker - d1-database
Sunderstood -- we're looking to add/adapt a postgres extension for d1 for our enterprise case but seems like gcp cloudsql might be better suited for this
KD1's limits and enabled extensions (like FTS5 or mathematical functions) are set at build-time and the same for everyone, so I'd probably agree that it's best to stick with a traditional offering if you want that sort of flexibility or customisation.
Lots of the limits are based on recommendations for untrusted inputs from https://www.sqlite.org/security.html.
Lots of the limits are based on recommendations for untrusted inputs from https://www.sqlite.org/security.html.
K[[env.staging.d1_databases]]K
toml
JIs this normal to nest D1 under the env? I didn't see this in other projects
IThat's because nesting it under env allows configuring different D1 databases per environment (where an environment is actually a separate worker suffixed with the environment name)
PHey is there a way to connect to D1 with Django now?
Sis there a way to make
wrangler d1 migrations apply not request user input ( to write y ). eg, --yes flag is used on some other wrangler commands to auto accept but does not work for migrations command.
CIt should skip user input if wrangle detects it’s a non-interactive environment or a CI environment. Try setting an environment variable of
CI-1
Sthanks.
CI=1 npx wrangler d1 migrations apply works.
Oanyone understand this error?
This is on an update - on logging the values being batched into the row, I dont see any values that are undefined.
The area where I am not sure is a field type of Blob, and I am trying to update it with an empty array - i.e.:
Does the blob type need to be a string or does it accept a pure array?
This is on an update - on logging the values being batched into the row, I dont see any values that are undefined.
The area where I am not sure is a field type of Blob, and I am trying to update it with an empty array - i.e.:
Does the blob type need to be a string or does it accept a pure array?
OActually, think I answered my own question... not sure what I was thinking 
the error message is a challenge though
the error message is a challenge though
NHey, quick question. When I do a simple select in a table with 100 rows using some constraints (let's say some column is > than a number) which satisfy only 5 rows, why does it say
rows_read: 100 (aka I get 100 billed rows)? Is it intended or is it a bug? Thanks
MYour query has to read the whole table to find those rows.
MIndexes enable D1 to improve query performance over the indexed columns for common (popular) queries by reducing the amount of data (number of rows) …
M(Noting that at 25 billion rows read per month included, you can make that query 250 million times. Don’t worry about optimizing small queries too quickly)
NThanks I'll look into it. This was an example, the table has 15k rows and it reads only 50 each time..
MNote that this is the same for any row-based relational database: you have to scan the table to find the rows that match the condition.
