On 4 February 2014 20:57, Roland Bock
On 2014-02-04 21:25, Rodrigo Madera wrote:
On Tue, Feb 4, 2014 at 6:11 PM, Mateusz Łoskot
wrote: I'd suggest to not to consider the two as competing libraries, but rather complementing.
I agree. I just thought of SOCI as a library that has already solved that problem. Thinking about it, I agree that they can complement each other.
Since sqlpp11 enforces compile time syntax it could help catch subtle errors very early.
In fact, there is room for some collaboration [2] "option would be to write a sqlpp11 connector library for SOCI"
The idea that it could build on SOCI would make it faster to develop and quite more stable, IMHO. It would give "instant support" for all SOCI backends.
Roland, What are your thoughts on this?
Regards, Rodrigo Madera
Mateusz and I exchanged a few mails. The consensus is that it is a very good idea and we want to do it. The main issue is time. We just don't have enough of it.
Indeed, unfortunately, but I'm staying hopeful about lots of improvements for SOCI 4 some time this year. (Please, help!)
So if you (or others) have time on your hands and are interest in this topic, why not write a SOCI connector for sqlpp11? A first version could probably be written without touching either sqlpp11 or SOCI.
I second that, this is great idea. It would also serve as a good test for soci through sqlpp11. By the way, there is another aspect of collaboration which I'd like to point out: maintenance of multi-DBMS abstraction layers is time consuming and testing it can easily become an ungrateful task, especially integration tests (including maintenance of required environments). So, tests and testing setups could be something to share. Best regards, -- Mateusz Łoskot, http://mateusz.loskot.net