1
Access 97 tested through ODBC 1998.04.19, by monty@mysql.com
3
Access 97 has a bug when on executes a SELECT follwed very fast with a
4
DROP TABLE or a DROP INDEX command:
6
[Microsoft][ODBC Microsoft Access 97 Driver] The database engine couldn't lock table 'crash_q' because it's already in use by another person or process. (SQL-S1
7
000)(DBD: st_execute/SQLExecute err=-1)
9
Debugging SQL queries in Access 97 is terrible because most error messages
12
Error: [Microsoft][ODBC Microsoft Access 97 Driver] Syntax error in CREATE TABLE statement. (SQL-37000)(DBD: st_prepare/SQLPrepare err=-1)
14
Which doesn't tell a thing!
18
Access 2000 tested through ODBC 2000.01.02, by monty@mysql.com
20
crash-me takes a LONG time to run under Access 2000.
22
The '1+NULL' and the 'OR and AND in WHERE' tests kills
23
Activestate Perl, build 521, DBI-DBC with an OUT OF MEMORY error.
24
The later test also kills perl/access with some internal errors.
25
To go around this one must run crash-me repeatedly with the --restart option.
27
Testing of the 'constant string size' (< 500K) takes a LOT of memory
28
in Access (at least 250M on My computer).
30
Testing of number of 'simple expressions' takes REALLY a lot of time
31
and memory; At some point I was up to 350M of used memory!
33
To fix the above, I modified crash-me to have lower max limits in the
36
Benchmarks (under Win98):
38
Running the connect-test will take up all available memory and this
39
will not be freed even after quitting perl! There is probably some
40
bug in the Access connect code that eats memory!
added
removed
tests/sql-bench/Comments/Access.crash-me
