mirror of https://github.com/SOCI/soci.git synced 2026-02-13 09:08:46 -06:00

Files

Mateusz Loskot 05ab0bcf6d Add SOCI_OVERRIDE macro as conditional C++11 override specifier

MSVC++ 1900+ always compile with C++11 mode enabled, so it should be
safe to selectively enable 'override'specifier for internal use.

It does not enable all C++11 features for SOCI and we still compile
with C++11 compilation mode SOCI_CXX_C11=OFF by default.

Refactoring performed with clang-tidy-4.0:

 cmake -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DSOCI_CXX_C11=ON ..
 run-clang-tidy.py -clang-tidy-binary -header-filter='.*' \
                   -checks='-*,modernize-use-modernize' -fix

2017-09-24 23:05:06 +02:00

db2

Add SOCI_OVERRIDE macro as conditional C++11 override specifier

2017-09-24 23:05:06 +02:00

empty

Add tests for some variants with char* query

2015-09-27 19:53:22 +02:00

firebird

Add SOCI_OVERRIDE macro as conditional C++11 override specifier

2017-09-24 23:05:06 +02:00

mysql

Add SOCI_OVERRIDE macro as conditional C++11 override specifier

2017-09-24 23:05:06 +02:00

odbc

Add SOCI_OVERRIDE macro as conditional C++11 override specifier

2017-09-24 23:05:06 +02:00

oracle

Add SOCI_OVERRIDE macro as conditional C++11 override specifier

2017-09-24 23:05:06 +02:00

postgresql

Add SOCI_OVERRIDE macro as conditional C++11 override specifier

2017-09-24 23:05:06 +02:00

sqlite3

Add SOCI_OVERRIDE macro as conditional C++11 override specifier

2017-09-24 23:05:06 +02:00

catch.hpp

moved to latest Catch UT Framework (#544 )

2017-07-07 21:31:41 +03:00

CMakeLists.txt

Request CATCH to disable all the C++11 features.

2015-09-27 18:54:55 +02:00

common-tests.h

Repair VC8 compile of test applications (#593 )

2017-09-23 12:57:38 +02:00

README.md

Move all tests from tests/assert to tests directory itself.

2015-04-01 14:41:35 +02:00

README.md

soci/tests

SOCI tests using CATCH testing framework live here.

Currently one test is built for each backend, i.e. there are soci_oracle_test, soci_postgresql_test, soci_sqlite3_test and so on and for ODBC backend there are multiple versions of the test depending on the ODBC driver used. Each of these tests can be run with a single parameter describing the database to use for testing in the backend-specific way as well as any of the standard CATCH command line options.