|Anonymous | Login | Signup for a new account||2020-08-06 13:35 UTC|
|Main | My View | View Issues | Change Log | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0008863||TestLink||Test Execute||public||2020-02-11 12:12||2020-07-22 13:14|
|Product Version||1.9.19 (2019 Q1)|
|Fixed in Version|
|Summary||0008863: DB Access Error - debug_print_backtrace() OUTPUT START - after setting testcase result|
|Description||When trying to execute a testcase and set the result, there's an error occuring sometimes (the result is always saved though):|
DB Access Error - debug_print_backtrace() OUTPUT START
ATTENTION: Enabling more debug info will produce path disclosure weakness (CWE-200)
Having this additional Information could be useful for reporting
issue to development TEAM.
#0 database->exec_query() called at [/var/www/html/lib/functions/testcase.class.php:8456]
In the closeOpenReqLinks function, in the DB_TYPE switch, there's no option for 'mysqli', just 'mysql' (the database type is 'mysqli' in my db_config file).
Changing or adding the switch option (case) for 'mysqli' fixes the problem.
|Additional Information||In Testlink version 1.9.20, the code looks like it has the same issue.|
|Tags||No tags attached.|
|QA Team - Task Workflow Status|
|Thanks I'm going to check|
theoretically, the installer does not write mysqli in the config_db.inc.php but mysql
can you confirm that the file was created by installer?
would you mind to provide your MySQL version, PHP Version?
You may be right, I think I had to change 'mysql' to 'mysqli' in the db_config, because the database connection didn't work right after the installation (PHP 7 doesn't support mysql, just mysqli commands).
Ok, now is clear. DB_TYPE in config has to be always mysql.
There is a logic that instruct TestLink regarding usage of correct PHP ADODB Driver
You're right, but there was some problem which was solved by changing the driver to 'mysqli' in config_db. After going back to mysql in condig_db everything seems to be fine, so the problem is solved now.
But regarding the 'mysqli' driver, I checked the installation scripts and there are case switches which take 'mysql' or 'mysqli' as the DB_TYPE, so something is already done in the scripts about the 'mysqli'.
|Hi, I just faced the issue somehow described in http://mantis.testlink.org/view.php?id=8686 [^] and seems the problem has been solved (in my case) by mentioned change DB_TYPE from mysql to mysqli - sorry have no idea what I did ;-)|
|2020-02-11 12:12||Kaa||New Issue|
|2020-02-11 15:31||fman||Note Added: 0029475|
|2020-02-11 15:35||fman||Note Added: 0029476|
|2020-02-12 13:02||Kaa||Note Added: 0029477|
|2020-02-12 15:59||fman||Note Added: 0029478|
|2020-02-20 07:55||Kaa||Note Added: 0029493|
|2020-02-20 11:00||Kaa||Note Added: 0029498|
|2020-02-21 07:48||Kaa||Note Deleted: 0029498|
|2020-07-22 13:14||texis||Note Added: 0029836|
|Copyright © 2000 - 2020 MantisBT Team|