Benjamin Maxwell
Benjamin Maxwell
There probably is not a super trivial fix, I imagine you will need to use LibUnicode to fix this
Just looking on my phone (so the code is not super easy to view), but I think the backdrop filter approach is not the right one for filter (but a...
I can't see any ways to check it the handle is still valid or even access the handle. It looks like the only way to know if it's valid still...
Seems like it. I couldn't figure out a great way of handling this (for postgres) but I've made up a quick hack that might work: ```c++ template class RobustPrepared {...
Not really getting any luck with it sadly. Still throws the same error & I'm not sure why.
Well it _sort of_ works but if I run an old prepared statement after reconnecting to the database my app seg faults (sometimes) as the old prepared statement references the...
Looks like I'll need to fork the connector to make this work. Though I'm not sure how to fix it really.
What does `conn->prepare` really return? I need to add a method to check if it's connection is current (as the easiest way to start handle things). @rbock
Thanks, I've got something that seems to work now: ```cpp template class RobustPrepared { Query const & preparable_query; public: RobustPrepared(Query const & query) : preparable_query{query} {}; template auto& prepare(Connection &...
@martinfalisse The child elements were not tested before, but it failed on the wpt.live tests without it (which uses them in every test) -- maybe add a few to your...