From 219bdeab80c06ea4ffc4f5333b58d27d0e588b4b Mon Sep 17 00:00:00 2001
From: Boris Kolpackov TEXT
.
The MySQL ODB runtime library also provides support for mapping the
- std::vector<char>
type to the MySQL BLOB types.
- However, this mapping is not enabled by default (by default,
- std::vector<char>
will be treated as a container).
+ std::vector<char>
and
+ std::vector<unsigned char>
types to the MySQL
+ BLOB types. However, this mapping is not enabled by default (by
+ default, std::vector
will be treated as a container).
To enable the BLOB mapping for this type we need to specify
the database type explicitly using the db type
pragma (Section 11.4.3, "type
"),
@@ -10413,9 +10414,10 @@ namespace odb
The SQLite ODB runtime library also provides support for mapping the
- std::vector<char>
type to the SQLite BLOB type.
- However, this mapping is not enabled by default (by default,
- std::vector<char>
will be treated as a container).
+ std::vector<char>
and
+ std::vector<unsigned char>
types to the SQLite
+ BLOB type. However, this mapping is not enabled by default (by default,
+ std::vector
will be treated as a container).
To enable the BLOB mapping for this type we need to specify
the database type explicitly using the db type
pragma (Section 11.4.3, "type
"),
@@ -11150,9 +11152,10 @@ CREATE TABLE Employee (
The PostgreSQL ODB runtime library also provides support for mapping the
- std::vector<char>
type to the PostgreSQL BYTEA
- type. However, this mapping is not enabled by default (by default,
- std::vector<char>
will be treated as a container).
+ std::vector<char>
and
+ std::vector<unsigned char>
types to the PostgreSQL
+ BYTEA
type. However, this mapping is not enabled by default
+ (by default, std::vector
will be treated as a container).
To enable the BYTEA
mapping for this type we need to specify
the database type explicitly using the db type
pragma (Section 11.4.3, "type
"),
--
cgit v1.1