Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
Useful in situations where the query is know to return at most one element
(*_one) or exactly one element (*_value).
|
|
Sections are an optimization mechanism that allows the partitioning of
data members of a persistent class into groups that can be separately
loaded and/or updated.
|
|
|
|
|
|
|
|
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.
|
|
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.
|
|
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.
|
|
|