On Mon, Mar 25, 2024 at 6:59 PM Julien Blanc
I agree with that. However, sqlite c++ wrappers have been here for ages, what's making the proposed boost.sqlite different from existing libraries? It's not so clear to me. I see two things that are not widespread:
* variant-base interface * json support
Did i miss others ?
- custom functions (scalar, aggregrate, windows) - event hooks - virtual tables
Peter pointed out that it might be a good idea to add some side to side comparison of using sqlite with using my library and he's correct since this does not seem apparent. But that's the problem this library tries to solve.
Another useful addition would be side-by-side comparison with sqlitecpp. As i understand from the docs, boost.sqlite has a few more features. Are the missing features what made the author start its own library?
That, minor design flaws, error handling & lacking view support.