ulib/3party/sqlpp11/docs/Tables.md
tqcq 99c258107b
All checks were successful
rpcrypto-build / build (Release, hisiv510.toolchain.cmake) (push) Successful in 1m24s
rpcrypto-build / build (Debug, himix200.toolchain.cmake) (push) Successful in 1m30s
rpcrypto-build / build (Debug, hisiv510.toolchain.cmake) (push) Successful in 1m43s
linux-mips64-gcc / linux-gcc-mips64el (push) Successful in 1m47s
linux-x64-gcc / linux-gcc (push) Successful in 2m11s
rpcrypto-build / build (Release, himix200.toolchain.cmake) (push) Successful in 3m19s
linux-hisiv500-gcc / linux-gcc-hisiv500 (push) Successful in 3m39s
feat/support_orm (#2)
Co-authored-by: tqcq <99722391+tqcq@users.noreply.github.com>
Reviewed-on: #2
2024-01-06 13:56:45 +00:00

641 B

Tables

In order to build meaningful SQL statements with sqlpp11, you need to represent tables and their columns as structs that can be understood by the library.

The default way to do so is by using a code generator to translate DDL to C++. A code generator covering a lot of use cases can be found here. There is also a specific one for sqlite3.

If you look at the output, you will see why a generator is helpful. Here is a sample.