Closed mutantdeveloper closed 8 years ago
What if we add the useful methods in database class like enable_foreign_keys() or error_code() instead of exposing internal pointer?
Added the methods. Let me know if you need more methods like these.
https://github.com/iwongu/sqlite3pp/commit/d755c07eba3cd623679ad30033aae343768b3bbe
adding methods is always good. But there are many sqlite3 functions that I am afraid won't all be supported in sqlite3pp any time soon. Exposing internal pointer is not neat, but who uses it should be at his own risk.
Do you have a list of functions in mind? I still prefer hiding the internal pointer in private.
For now, I think changes() and extended_error_code() will be helpful
As I wrote, they are already added in https://github.com/iwongu/sqlite3pp/commit/d755c07eba3cd623679ad30033aae343768b3bbe Git-pull to see them.
There are many sqlite3 features that are not supported by sqlite3pp::database. As a workaround, it would be nice if user can use the internal sqlite3* pointer.
Some useful features that are not supported;