On Wed, Feb 5, 2014 at 9:57 PM, Roland Bock
Maybe if SOCI creates it's own expression grammar for SQL queries it would be a faster and more practical solution, since SOCI has been around for quite some time and has solved several issues along the way. And the expression tree for SQL queries is the fastest part of such a library. The eye candy and sugar should be easy to convert to string and use the SOCI engine for it.
Sqlpp11 will still need to reimplement what SOCI has done several years ago. No. It will not. sqlpp11 will not touch databases, but only glue code...
I would add that SOCI would still have to handle raw string for SQL, because there are things that are specific to one database and cannot even be expressed in another DBMS. And we often need them. It's bad to say to someone "you have to stuck to the lowest common denominator" if he only uses one DBMS. So, you would have two different syntax for the same library... quite strange. Better to split it in 2 differents lib parts like this I think. -- Cheers Johan