3 ms·
If I understand correctly, what this project does is take the actual postgresql sources, which are written in C, compile them to wasm and provide typescript wra
by OvbiousError 10mo ago
If I understand correctly, what this project does is take the actual postgresql sources, which are written in C, compile them to wasm and provide typescript wrappers. So you need the wasm to be able to use the C code from js/ts.
- mpweiher 10mo agoYes. I would like to use the code as a library from something other than js/ts.
- monster_truck 10mo agoSo compile it and use it?
- embedding-shape 10mo agoSounds you only need to create the APIs for calling into WASM if so, so as long as your language of choice can do that, you're good to go.
- dboreham 10mo agoThat adds extra unnecessary complexity. The code is written in C. There are C compilers for all CPUs. So just call the C code from <other language that's not JS>.
- hombre_fatal 10mo agoWell, a project has scope. Looking at the repo, it started as postgres-in-the-browser. An abstract interface with C and wasm as targets is just more scope. But it looks like the hard part of patching postgres to librar-ify it is already done agnostically in C. So you just need to ctrl-f for "#if defined(__EMSCRIPTEN__)" to impl those else branches and port the emmake file to make.
- mirrir 10mo agoYou can use it in Rust if you like. I've used pglite through wasmer before. Also [pglite-oxide](https://lib.rs/crates/pglite-oxide https://lib.rs/crates/pglite-oxide) is pretty usable.