sweet, when can we expect read replicas to be enabled?
sweet, when can we expect read replicas to be enabled?
MThe Cloudflare Blog
D1 is now in open beta, and the theme is “scale”: with higher per-database storage limits and the ability to create more databases, we’re unlocking the ability for developers to build production-scale applications on D1
Uso what exactly is the spec for
I've got a column defined as
TIMESTAMP columns?I've got a column defined as
created_at TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP, and that produces values like 2023-10-16 15:56:51, but what actual format is that so I can convert to ISO 8601-1:2019 properly?
Ddate() time() YYYY-MM-DD HH-MM-SS
DInterestingly I just researched this very thing 30 mins ago for my own project. D1 is basically just SQLite so you can see the info in the sqlite documentation https://www.sqlite.org/lang_datefunc.html
Uheh.
except the sqlite documentation sucks and says it is iso8601, when it in fact isn't
except the sqlite documentation sucks and says it is iso8601, when it in fact isn't
DMight be because sqlite.org is refrencing the 8601 Steptember 1997 standarization format while what you need is 2019
DIf you dont mind me asking, why do you need that specific standardization?
Unope its just noncompliant. iso8601 specifically does not allow space as separator, what sqlite actually uses is RFC3339
Ubecause 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