Add synchronous execute function

[rikur]

Fixes #173

Add synchronous execute API to the project.

• cpp/DBHostObject.cpp
  • Add a new executeSync function for synchronous execution.
  • Directly call opsqlite_execute without using invokeAsync.
  • Register the new executeSync function in the function map.
• cpp/libsql/bridge.cpp
  • Add a new executeSync function for synchronous execution.
  • Directly call libsql_query_stmt without using libsql_prepare.
• cpp/DBHostObject.h
  • Declare the new executeSync function.
• cpp/libsql/bridge.h
  • Declare the new executeSync function.
• example/src/tests/queries.spec.ts
  • Add test cases for the new executeSync function.

---

For more details, open the Copilot Workspace session.

[rikur]

Testing Github Copilot Workspace.

[rikur]

@ospfranco if you don't mind having a look. I have near zero experience with JSI or C++, this implementation was done 90% by AI given the instructions you posted here: #173 (comment)

I had to manually remove a couple mistakes the AI made, but other than that, it looks pretty darn good to my eyes.

[rikur]

I couldn't really run the JS / react-native tests, I think my environment is not setup correctly. Instructions on how to setup the dev environment could me useful.

I'll mark this ready for review for the CI to run the tests.

[rikur]

Oh, and if the code is garbage, please feel free to close this. In that case, I apologize for the noise :)

[ospfranco]

It's wrong. But if you don't mind, I'm waiting for Rodrigo to take a look. There's more behind it than just code. Thanks anyways!

[rikur]

Great news, maybe us developers get to keep our jobs for a bit longer then 😛

[gituser8796]

hi @ospfranco - do you think we can give it priority? we're using the sync version and it will require us to make some changes. also, what will be the performance gain when using async compared to sync? will it clone the object for example?

[ospfranco]

There is no performance difference between async and sync, at most there is a small penalty to schedule work on the JS runtime, the code is the same with the exception it's executed in a different thread.

We will get to it when we can, we are just busy with paid work atm.