(See #190)
The explicitly deleted copy-assignment operator of SQLite::Statement stops the compiler from generating a move-assignment operator for this type. On a related note, having a default constructor would also be nice. Consider the following example that I would wish to be able to write:
struct foo
{
SQLite::Database db;
SQLite::Statement st;
foo()
: db(path, SQLite::OPEN_READWRITE)
{
// do stuff with db
st = SQLite::Statement("SQL CODE");
}
};Currently, I have to box all statements that I use in this way into optionals. Ugly!
(See #190)
The explicitly deleted copy-assignment operator of
SQLite::Statementstops the compiler from generating a move-assignment operator for this type. On a related note, having a default constructor would also be nice. Consider the following example that I would wish to be able to write:Currently, I have to box all statements that I use in this way into
optionals. Ugly!