Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
Now objects are always loaded as non-const and the object cache in
session treats all objects as non-const.
|
|
|
|
Also delay getting a connection until after we do all the sanity
checks (e.g., that there is no active transaction). Otherwise we
are running risk of getting blocked rather than throwing an
exception.
|
|
New test: common/erase-query. Documentation is in Section 3.9, "Deleting
Persistent Objects". The current implementation does not work well with
the session (no removal of the erased objects from the cache).
|
|
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.
|
|
New object pragma: callback. New test: common/callback. New manual
section: 10.1.4, "callback".
|
|
New test: mysql/native. New manual section: 3.9, "Executing Native SQL
Statements".
|
|
|
|
Currently, session is just an object cache. The persist, update, and
erase database operations are overloaded to also work on object
pointers. All the database operations and the query facility now
support const objects.
New session-related exceptions: not_in_session, already_in_session,
const_object.
|
|
|
|
|
|
|