C++ SOCI

今天看项目，看到一个用法

sql->once << "sqlstring..." ,into(s1),into(s2)...  不甚理解，于是问项目组的老大，老大给我讲了这个sql的用法，

说上面这个是sql语句的立即执行，然后把执行语句后查询出来的内容传到元组项s1，s2里面

然后还有比如 sql->prepare  则是把语句先缓存起来，等待一定时间之后或者积累了很多条之后，进行批处理执行

大开眼界，以前完全不知道有这样的c++的用法，找到了一些完整的概念说明和用法

SOCI is a database access library for C++ that makes the illusion of embedding SQL queries in the regular C++ code, staying entirely within the Standard C++.

The idea is to provide C++ programmers a way to access SQL databases in the most natural and intuitive way. If you find existing libraries too difficult for your needs or just distracting, SOCI can be a good alternative.

The simplest motivating code example for the SQL query that is supposed to retrieve a single row is:

int id = ...;
string name;
int salary;

sql << "select name, salary from persons where id = " << id,
       into(name), into(salary);

and the following benefits from extensive support for object-relational mapping:

int id = ...;
Person p;

sql << "select first_name, last_name, date_of_birth "
       "from persons where id = " << id,
       into(p);

Integration with STL is also supported:

Rowset<string> rs = (sql.prepare << "select name from persons");
copy(rs.begin(), rs.end(), ostream_iterator<string>(cout, "\n"));

SOCI offers also extensive integration with Boost datatypes (optional, tuple and fusion) and flexible support for user-defined datatypes.

Even though SOCI is mainly a C++ library, it also allows to use it from other programming languages. Currently the package contains the Ada binding, with more bindings likely to come in the future.

Starting from its 2.0.0 release, SOCI uses the plug-in architecture for backends - this allows to target various database servers. Currently (3.2.1), the following database systems are supported:

• DB2
• Firebird
• MySQL
• ODBC (generic backend)
• Oracle
• PostgreSQL
• SQLite3

The intent of the library is to cover as many database technologies as possible. For this, the project has to rely on volunteer contributions from other programmers, who have expertise with the existing database interfaces and would like to help writing dedicated backends.