Database-related type system concepts.
|
| interface | Array |
| | Array concept represents PostgreSQL array. More...
|
| |
| interface | Composite |
| | Composite concept represents PostgreSQL composite types. More...
|
| |
|
| template<typename T > |
| constexpr bool | ozo::BuiltIn |
| | Condition indicates if the specified type is built-in for PG. More...
|
| |
| template<typename T > |
| constexpr auto | ozo::DynamicSize |
| | Condition indicates if the specified type is has dynamic size. More...
|
| |
| template<typename T > |
| constexpr auto | ozo::StaticSize |
| | Condition indicates if the specified type is has fixed size. More...
|
| |
| template<typename T > |
| constexpr auto | ozo::OidMap |
| | Map of C++ types to corresponding PostgreSQL types OIDs. More...
|
| |
◆ BuiltIn
template<typename T >
| constexpr bool ozo::BuiltIn |
|
constexpr |
Condition indicates if the specified type is built-in for PG.
- Template Parameters
-
◆ DynamicSize
template<typename T >
| constexpr auto ozo::DynamicSize |
|
constexpr |
Condition indicates if the specified type is has dynamic size.
- Template Parameters
-
◆ OidMap
template<typename T >
| constexpr auto ozo::OidMap |
|
constexpr |
Map of C++ types to corresponding PostgreSQL types OIDs.
OidMap is needed to store information about C++ types and corresponding custom database types' OIDs. For PostgreSQL built-in types no mapping is needed since their OIDs are defined in PostgreSQL sources. For custom types their OIDs are defined in a database.
OidMap Definition
OidMap map is an object for which these next statements are valid:
set_type_oid<T>(map, oid);
Sets oid for type T in the map.
oid_t oid = type_oid<T>(map);
Returns oid value for type T from the map.
Returns true if map has no types OIDs.
- See also
- oid_map_t, register_types(), set_type_oid(), type_oid(), accepts_oid()
◆ StaticSize
template<typename T >
| constexpr auto ozo::StaticSize |
|
constexpr |
Condition indicates if the specified type is has fixed size.
- Template Parameters
-