|Anonymous | Login | Signup for a new account||2020-02-25 08:26 UTC|
|Main | My View | View Issues | Change Log | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0002662||TestLink||Database General||public||2009-06-25 17:00||2010-05-01 20:34|
|Fixed in Version||1.9 Beta 2|
|Summary||0002662: SQL error in execute view|
|Description||An SQL error is shown in execute testcase view. It said column was missing in req_coverage table|
A simple solution was to change lowercase to UPPERCASE in sql
|Tags||No tags attached.|
|QA Team - Task Workflow Status|
|Attached Files||014_fix_CASE_in_requirements.patch [^] (670 bytes) 2009-06-25 17:00 [Show Content]|
|pls mention the build this error was found in ?|
The nightly build from today
Is there no way of setting the dev version in this bug tracker?
|also specify database!|
I'm using MySQL 5.1
Don't know if this is specific to MySQL...
But the patch uses the same style as other querys in TL, so it should be compatible with other databases as well
To be clear, this is not an error in the database. It is only the query
Any update on this?
The problem still exists in CVS...
The fix is simple:
In file lib/functions/requirement_mgr.class, line 751 change:
" NHB.name AS req_spec_title,req_coverage.testcase_id " .
" NHB.name AS req_spec_title,REQ_COVERAGE.testcase_id " .
edited on: 2009-10-12 02:25
I am not sure if the column names are case specific in Mysql ? Is it ?
Please check once.
NOTE: Also how do you reproduce this issue?
It is case-sensitive on my linux system at least.
From the manual (http://dev.mysql.com/doc/refman/5.0/en/identifier-case-sensitivity.html [^])
> Although database and table names are not case sensitive on some platforms,
> you should not refer to a given database or table using different cases
> within the same statement. The following statement would not work because it
> refers to a table both as my_table and as MY_TABLE:
> mysql> SELECT * FROM my_table WHERE MY_TABLE.col=1;
The above is this specific problem. And I think we should always use the correct case (even if it in some cases doesn't matter)
I reproduce this by going to execute and selecting a test case. In the right view I get the error message. (I've tried disabling requirements for the test project but no difference)
|test must be made on postgres|
|2009-06-25 17:00||Eloff||New Issue|
|2009-06-25 17:00||Eloff||File Added: 014_fix_CASE_in_requirements.patch|
|2009-06-25 18:56||techieguy||Note Added: 0007341|
|2009-06-25 19:15||Eloff||Note Added: 0007342|
|2009-06-26 01:12||schlundus||Note Added: 0007347|
|2009-06-29 20:14||Eloff||Note Added: 0007386|
|2009-10-09 02:23||Eloff||Note Added: 0008059|
|2009-10-12 02:24||amitkhullar||Note Added: 0008063|
|2009-10-12 02:25||amitkhullar||Note Edited: 0008063|
|2009-10-12 02:39||Eloff||Note Added: 0008065|
|2009-11-02 06:08||Eloff||Status||new => resolved|
|2009-11-02 06:08||Eloff||Fixed in Version||=> 1.9 (DEV)|
|2009-11-02 06:08||Eloff||Resolution||open => fixed|
|2009-11-02 06:08||Eloff||Assigned To||=> Eloff|
|2009-11-02 23:51||fman||Note Added: 0008194|
|2010-05-01 20:34||fman||Status||resolved => closed|
|Copyright © 2000 - 2020 MantisBT Team|