OpenDBX/Test application - Revision history

Nose: /* Examples */

2010-05-08T20:27:09Z

‎Examples

Nose: /* Options */

2010-05-08T20:21:22Z

‎Options

Nose: /* Options */

2010-05-08T20:13:46Z

‎Options

Nose: /* Description */

2010-05-08T17:58:38Z

‎Description

Nose: Initial descriptions

2010-05-08T17:49:01Z

Initial descriptions

New page

There are two applications for testing the OpenDBX library and their backends available when building the library from source.

== Name ==

These to applications can be found in the "test" sub-directory of the extracted tarball:

./test/odbxtest
./test/odbxplustest

The first one (odbxtest) uses the C library functions available from libopendbx while the second one (odbxplustest) executes the same statements by using the C++ objects from libopendbxplus.

== Sypnosis ==

./test/odbxtest -b <backend or library>
-h <host or IP or directory> [-p <port>]
-d <database or file name> -u <user name>
-w <password> [-r <runs>] [-e]

./test/odbxplustest -b <backend or library>
-h <host or IP or directory> [-p <port>]
-d <database or file name> -u <user name>
-w <password> [-r <runs>] [-e]

== Description ==

The applications execute a test suite containing a predefined set of SQL statements against your server. This includes creating a table, inserting rows, performing multiple SELECT, UPDATE and DELETE statements (also within transactions if supported). It also removes the created table and tests for certain error conditions.

@@ Line 46: / Line 46: @@
 == Examples ==
-MySQL server
+MySQL with encrypted connections
   ./test/odbxtest -b ./backends/mysql/.libs/libmysqlbackend.so
-    -h 127.0.0.1 -d odbx -u odbx -w odbx
+    -h 127.0.0.1 -d odbx -u odbx -w odbx -e
-SQLite3
+SQLite 3 using file in ./test/odbx.sq3 (will be created if it doesn't exist)
   ./test/odbxtest -b ./backends/sqlite3/.libs/libsqlite3backend.so
     -h ./test/ -d odbx.sq3
-Oracle
+Oracle with required port parameter
   ./test/odbxtest -b ./backends/oracle/.libs/liboraclebackend.so
     -h localhost -p 1521 -d ODBX -u odbx -w odbx

← Older revision		Revision as of 20:21, 8 May 2010
Line 43:		Line 43:

	; -e : Enable encryption to the database server if supported (optional)		; -e : Enable encryption to the database server if supported (optional)
		+
		+	== Examples ==
		+
		+	MySQL server
		+
		+	./test/odbxtest -b ./backends/mysql/.libs/libmysqlbackend.so
		+	-h 127.0.0.1 -d odbx -u odbx -w odbx
		+
		+	SQLite3
		+
		+	./test/odbxtest -b ./backends/sqlite3/.libs/libsqlite3backend.so
		+	-h ./test/ -d odbx.sq3
		+
		+	Oracle
		+
		+	./test/odbxtest -b ./backends/oracle/.libs/liboraclebackend.so
		+	-h localhost -p 1521 -d ODBX -u odbx -w odbx

@@ Line 28: / Line 28: @@
 == Options ==
-; -b <backend> : name of the database backend or path to the backend library
+; -b <backend> : Name of the database backend (see list of [[OpenDBX/Support|supported backends]]) or path to the backend library (e.g. "./backends/mysql/.libs/libmysqlbackend.so")
-; -h <host> : host name, IP address or directory path to the database file
+; -h <host> : Host name, IP address or directory path to the database file. Look at the [[OpenDBX/Configuration|database specific configuration]] for details

← Older revision		Revision as of 17:58, 8 May 2010
Line 25:		Line 25:

	The applications execute a test suite containing a predefined set of SQL statements against your server. This includes creating a table, inserting rows, performing multiple SELECT, UPDATE and DELETE statements (also within transactions if supported). It also removes the created table and tests for certain error conditions.		The applications execute a test suite containing a predefined set of SQL statements against your server. This includes creating a table, inserting rows, performing multiple SELECT, UPDATE and DELETE statements (also within transactions if supported). It also removes the created table and tests for certain error conditions.
		+
		+	== Options ==
		+
		+	; -b <backend> : name of the database backend or path to the backend library
		+
		+	; -h <host> : host name, IP address or directory path to the database file