seth
Explore posts from serversDTDrizzle Team
•Created by seth on 3/15/2025 in #help
Stack trace on constraint failed doesn't include my application code
In contrast, throwing an async error inside a nuxt 3 event handler doesn't normally result in a "disconnected" stack trace, for example:
Results in the connected stack trace (note the first line references server/api/session[id].get.ts):
11 replies
DTDrizzle Team
•Created by seth on 3/15/2025 in #help
Stack trace on constraint failed doesn't include my application code
Here's a "minimal repro" example with nuxt 3, maybe this will inspire somebody:
If I comment out the with(), everything works, its a valid query. The with just makes the query invalid, and it results in a stack trace without the application code in the stack like:
11 replies
DTDrizzle Team
•Created by seth on 3/15/2025 in #help
Stack trace on constraint failed doesn't include my application code
something nuxt is doing or something I'm doing wrong with nuxt I should say lol
11 replies
DTDrizzle Team
•Created by seth on 3/15/2025 in #help
Stack trace on constraint failed doesn't include my application code
Yeah, I suspected the async chain too, I always get a little confused at this point lol. That's why I hoped --trace-uncaught would change things, but no luck.
I'm seeing this in another context too, I'm wondering if something nuxt is doing is making this more likely to happen.
11 replies
DTDrizzle Team
•Created by seth on 3/15/2025 in #help
Stack trace on constraint failed doesn't include my application code
No prepared statements, although using them is one of my next ideas. Do you ever see this issue, or is this particular to me?
11 replies