Fix for Bug 6602 - Reports dictionary doesn't properly recognize text columns
Reports dictionary won't let you set a comparison for MEDIUMTEXT columns. To test, choose a MEDIUMTEXT column like borrowers.surname in Step 3 of adding a new dictionary definition. Before the patch, in Step 4 you would not see any kind of form field for entering a comparison. After patching Step 4 will offer you a field labeled "Search string matches." Signed-off-by: Katrin Fischer <Katrin.Fischer.83@web.de> Fixes described problem with mediumtext columns. Signed-off-by: Chris Cormack <chrisc@catalyst.net.nz>
This commit is contained in:
parent
73081505f5
commit
df2a3a9a3c
1 changed files with 1 additions and 1 deletions
|
@ -115,7 +115,7 @@ elsif ($phase eq 'New Term step 4'){
|
|||
if ($type eq 'DATE' || $type eq 'DATETIME'){
|
||||
$tmp_hash{'date'}=1;
|
||||
}
|
||||
if ($type eq 'TEXT'){
|
||||
if ($type eq 'TEXT' || $type eq 'MEDIUMTEXT'){
|
||||
$tmp_hash{'text'}=1;
|
||||
}
|
||||
# else {
|
||||
|
|
Loading…
Reference in a new issue