Age | Commit message (Collapse) | Author | Files | Lines |
|
Now in libodb the odb::core namespace is split into odb::common (database-
independent stuff) and odb::core proper, which imports odb::common. Each
database runtime now defines odb::<db>::core namespace which also imports
odb::common and adds the database-specific bits. The overall idea is that
one can do using namespace odb::<db>::core just like for odb::core.
|
|
All generated code now includes database id. The database-specific
database class interface has been updated to include all the database
operations. The database-specific tests now use this interface.
|
|
|
|
|
|
Too much effort to maintain.
|
|
|
|
New pragma id (object). New test: common/no-id.
|
|
Also add the initial infrastructure for the readonly members support.
Right now the split insert/update bindings allows us to avoid sending
object id in UPDATE statements. It will also allows us to support
readonly members.
|
|
|
|
This abstract class represents a connection to the database. One can
use it to start a transaction or to execute a native statement out
of a transaction.
Before we had concrete connection classes in the database runtime
libraries (e.g., odb::mysql::connection). Now these classes derive
from odb::connection.
|
|
This will allow us to reuse things more.
|
|
|
|
|
|
Generalize statements that were used for persisting objects to work for
both objects and containers. Implement a cache for container statements.
|
|
|
|
|
|
|
|
|