I've pasted a 500KB query in there, 2200 rows inserted no worries
I've pasted a 500KB query in there, 2200 rows inserted no worries
Mmight lag tho
D140k here
Dgood news, the console seems to be better than wrangler. Inserted 140k rows in about 15s no problem.
Thank you for the suggestion, props to whoever worked on this feature its amazing
Thank you for the suggestion, props to whoever worked on this feature its amazing
Mthanks 
JIs there a timeline of when things are announced like pricing announced with beta. not like eta but what features will be shipped
Mit's super gross but
wrangler d1 create <db-preview> wrangler d1 delete <db-preview> might do the trick?M(that's how i handle previews for Workers personally)
Mah yep. forgot about that
Mprobably easier to do in json mode
E
Mnope, not yet
EThe best you'll get is 
, although bear in mind it's still alpha, if we're lucky possibly near the end of the year but personally I wouldn't put a large bet on that
For comparison:
R2 entered open beta in May 22, went GA Sept 22
Pages functions entered open beta in Nov 21, went GA in Nov 22
DO entered open beta in Mar 21, went GA Nov 21
, although bear in mind it's still alpha, if we're lucky possibly near the end of the year but personally I wouldn't put a large bet on thatFor comparison:
R2 entered open beta in May 22, went GA Sept 22
Pages functions entered open beta in Nov 21, went GA in Nov 22
DO entered open beta in Mar 21, went GA Nov 21
Sshould I store markdown documents directly in d1 or use r2?
MWhat’s the schema? It’s not just the number of rows: it’s a function of (rows x row size) - you’re doing a full table scan. The alpha is a real alpha — there are many rough edges. Performance & scalability included.
(We’re very, very confident about the new architecture, but the alpha is “as is” right now)
(We’re very, very confident about the new architecture, but the alpha is “as is” right now)
MThe multiple FK relationships mean it’s not just that one table. But regardless (and echoing our docs): the alpha is not suitable for production workloads. As schema, query and overall table complexity increases, there are known failure modes.
MWe haven’t made any timelines public just yet.
MAll I can say is soon
Mnot pricing related: but I don't think D1 is suited for write-intensive applications, compared to like, analytics engine