diff options
author | Constantin Michael <constantin@codesynthesis.com> | 2011-03-22 10:49:56 +0200 |
---|---|---|
committer | Constantin Michael <constantin@codesynthesis.com> | 2011-04-22 17:54:50 +0200 |
commit | 8e29be9f2229a6c618f95b725502f7082f02d50a (patch) | |
tree | 77eb79933015300a398a10135122534bfa5abaa3 /qt/README | |
parent | d206125ed2d85891d946c3c12c9b7eb95d5af41e (diff) |
Add Qt profile example
Diffstat (limited to 'qt/README')
-rw-r--r-- | qt/README | 56 |
1 files changed, 56 insertions, 0 deletions
diff --git a/qt/README b/qt/README new file mode 100644 index 0000000..4e94255 --- /dev/null +++ b/qt/README @@ -0,0 +1,56 @@ +This example shows how to persist objects that use Qt smart pointers, +containers, and value types with the help of the Qt profile library +(libodb-qt). + +The example consists of the following files: + +employee.hxx + Describe contents. + +employee-odb.hxx +employee-odb.ixx +employee-odb.cxx +employee.sql + The first three files contain the database support code and the last file + contains the database schema for the employee.hxx header. + + These files are generated by the ODB compiler from employee.hxx using the + following command line: + + odb -d <database> -p qt --generate-schema --generate-query employee.hxx + + Where <database> stands for the database system we are using, for example, + 'mysql'. + + The -p option is used to instruct the ODB compiler to load the Qt + profile. + +database.hxx + Contains the create_database() function which instantiates the concrete + database class corresponding to the database system we are using. + +driver.cxx + Driver for the example. It includes the employee.hxx and employee-odb.hxx + headers to gain access to the persistent classes and their database support + code. It also includes database.hxx for the create_database() function + declaration. + + In main() the driver first calls create_database() to obtain the database + instance. It then creates a number of 'employee' and 'employer' objects and + persists them in the database. The next transaction loads all the employees + of a particular employer using the employee-employer relationship. Finally, + the driver performs a database query which uses a data member of the Boost + gregorian::date type in its criterion. + +To run the example we first need to create the database schema. Using MySQL +as an example, this can be achieved with the following command: + +mysql --user=odb_test --database=odb_test < employee.sql + +Here we use 'odb_test' as the database login and also 'odb_test' as the +database name. + +Once the database schema is ready, we can run the example (using MySQL as +the database): + +./driver --user odb_test --database odb_test |