That's probably an underlying error from Durable Objects that we shouldn't surface to users since yo
That's probably an underlying error from Durable Objects that we shouldn't surface to users since you don't manage the underlying DOs and cannot run that anyway through D1.
What SQL did you try to run that gave you that error? I don't think I saw it before surfacing to users.
To summarize about transactions, since D1 is remote from your worker the traditional transaction approach of opening a transaction and interleaving JS code with SQL doesn't work (at least with the current implementation). The D1 batch query runs all the given queries within a transaction if you want multiple statements to be executed atomically.
What SQL did you try to run that gave you that error? I don't think I saw it before surfacing to users.
To summarize about transactions, since D1 is remote from your worker the traditional transaction approach of opening a transaction and interleaving JS code with SQL doesn't work (at least with the current implementation). The D1 batch query runs all the given queries within a transaction if you want multiple statements to be executed atomically.
![beingmudit [WePlayDOS]](https://cdn.discordapp.com/embed/avatars/1.png)
