Development and Releases about sqlite_modern_cpp HOT 8 OPEN

It's been a while i wanted to integrate SQLCipher.
Also supporting other databases (mysql for example) will be another option to consider.

what do you think ?

from sqlite_modern_cpp.

The SQLCipher stuff looks interesting but i dont think i will need it.

As for more DBs i dread the incompatibilitys but i welcome more options, and indeed i will need mysql or postgress support in a few month ...

Whats youre opinion on breaking changes? I'm a fan of major breaks every major release so we can keep it modern. So this version would be v1.5 but if we had introduced the new operators and removed the current operator>> it would have bin v2.

from sqlite_modern_cpp.

That does make sense, major versions would be because of major API changes.

and yes incompatibilitys will be a big challenge .

from sqlite_modern_cpp.

IIRC sqlcipher just needs an extra call (to set the encryption keyword), everything else is api compatible to sqlite, i.e. you can replace sqlite3.c & sqlite3.h from those from sqlcipher and insert the extra call in the right sequence and nothing else is required for compiling. But for link you need the openssl's libcrypto.

from sqlite_modern_cpp.

So it took almost a year but now we got a new Version. ;)

from sqlite_modern_cpp.

Seems like there have been quite a few changes since the 3.2 release - time for another one? 😉

from sqlite_modern_cpp.

// overload >> for Rvalue containers (1)
auto numbers = db << "select numbers from tbl where id = ?" << 1 >> vector<int>();
// support operator >> for Rvalue containers of std::tuple (2)
auto poeple = db << "select age,name from tbl;" >> vector<tupe<int,string>>();

// single row blob (3)
vector<int> vblob;
db << "select numbers from tbl where id = 1" >> blob_t(vblob);
// multiple row int
vector<int> vrows;
db << "select age from tbl;" >> vrows;

For v4 i was thinking to get 1,2 & 3 implemented, cause 3 is a breaking change.
(The interface above is "my" summery of #122)

If anyone wants to work on the above please give me a heads up, so we don't work on the same thing :-)
Let's put end of October as the deadline! If we have the above i'll release it as v4 otherwise it'll be v3.3.

from sqlite_modern_cpp.

The deadline is passed, i still want to get those features in before a new release but lack the motivation to work on it.

btw, a piece of good news, we are now listed on https://github.com/rigtorp/awesome-modern-cpp

from sqlite_modern_cpp.