You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Timothy Pearson
f0de9e167e
|
13 years ago | |
|---|---|---|
| .. | ||
| Makefile.am | 13 years ago | |
| README | 15 years ago | |
| cursors_test.h | 15 years ago | |
| dbcreation_test.h | 15 years ago | |
| dr_prop_test.h | 13 years ago | |
| main.cpp | 13 years ago | |
| mysqlcursor.cpp | 14 years ago | |
| mysqlcursortest_create.sql | 15 years ago | |
| mysqlcursortest_expectedoutput | 15 years ago | |
| newapi.pro | 13 years ago | |
| parser_test.h | 13 years ago | |
| schema.sql | 15 years ago | |
| schema_test.h | 15 years ago | |
| sqltest | 15 years ago | |
| sqltest_int | 15 years ago | |
| statements.txt | 14 years ago | |
| tables_test.h | 14 years ago | |
| tableview_test.h | 14 years ago | |
README
1. kexidbtest ------------- This is a set of tests for the new, common KexiDB API. Every test is driver-independent. Usage: run 'kexidbtest --help' for usage details. 2. sqltest ---------- Script for easier executing 'parser' subtest within kexidbtest. Usage: run './sqltest' without arguments for usage details. There is also sqltest_int script accepting interactive mode. Usage: run './sqltest_int' without arguments for usage details. 3. Important documents ---------------------- -Kexi API Documentation in html http://koffice.org/developer/apidocs/kexi/html -KexiDB Drivers section of KexiWiki Web Page http://www.kexi-project.org/wiki/wikiview/index.php?KexiDBDrivers 4. Information for KexiDB drivers developers -------------------------------------------- While you're developing new driver or improving existing one, you may want to test a number of aspects to see if the behaviour looks like expected. Following tests should be passed (the order is from most simple test to more complicated): -dbcreation -schema -tables -cursors -tableview -parser -dr_prop If the given driver does not pass one of these tests, and you have found: - that the problem is at the KexiDB library side (e.g. crash, or improper behaviour), or - that the problem can be solved by extending KexiDB API, or - that the documentation is not correct or not enough detailed, or - whatever like that, ..please contact: KexiDB maintainer Jaroslaw Staniek, js @ iidea . pl, irc://irc.freenode.net #kexi