-
Notifications
You must be signed in to change notification settings - Fork 480
RFC1
mloskot edited this page Apr 26, 2013
·
23 revisions
- Author: Mateusz Loskot
- Date: (not proposed yet)
- Version: 4.0.0
- Status: development
Main purpose of this proposal is to:
- clarify status of C++ integer types supported by
use()
andinto()
- decide on what C++ integer types should be supported in SOCI
- propose implementation of type conversions
- describe handling of boundary and corner cases, and any heuristics involved
in order to provide required C++ integer types support for all database backends available in SOCI.
- TODO: Decide on C++03 integer types support
The following table presents mapping of C++ integer types to corresponding SQL types planned to implement in SOCI. If direct mapping is not possible, an appropriate conversion should be implemented, with careful explanation of how it handles edge cases, integer overflow and errors.
C++11 | ANSI SQL | Firebird | ODBC | Oracle | MySQL | PostgreSQL | SQLite3 |
---|---|---|---|---|---|---|---|
int8_t | |||||||
uint8_t | |||||||
int16_t | |||||||
uint16_t | |||||||
int32_t | |||||||
uint32_t | |||||||
int64_t | |||||||
uint64_t |
- What is status of integer types support? thread on soci-users
- Integer types support (and type conversion in general thread on soci-devel