0044744: WADvalidation fails when using PostgreSQL 13 beta2 with : "could not determine which collation to use for string comparison"

Description

WADvalidation step (part of install.source or compile) fails when using pg13 beta2 with following error:

[WADValidation] 157686 [main] ERROR org.openbravo.wad.validation.WADValidatorData - SQL error in query: select t.tablename||'.'||c.columnname as objectName, 'DB Column Name' as objectType, c.columnname as currentValue, (select max(name) from AD_Module_DBPrefix dbp where dbp.AD_Module_ID = c.AD_Module_ID) as expectedvalue, m.name as moduleName, m.ad_module_id as moduleId from ad_table t, ad_module m, ad_package p, ad_column c where t.ad_package_id = p.ad_package_id and t.ad_table_id = c.ad_table_id and c.ad_module_id != p.ad_module_id and m.ad_module_id = c.ad_module_id and not exists (select 1 from ad_module_dbprefix dbp where instr(upper(c.columnname), 'EM_'||upper(dbp.name)||'_') = 1 and dbp.ad_module_id = c.ad_module_id) AND NOT EXISTS( SELECT 1 FROM AD_EXCEPTIONS WHERE TYPE='COLUMN' AND UPPER(NAME2)=UPPER(T.Tablename) AND UPPER(NAME1)=UPPER(c.Columnname)) and (1=1 and m.javapackage in ('%') or to_char('Y')=to_char(?)) union select t.tablename||'.'||c.columnname as objectName, 'Name' as objectType, to_char(c.name) as currentValue, (select max(name) from AD_Module_DBPrefix dbp where dbp.AD_Module_ID = c.AD_Module_ID) as expectedvalue, m.name as moduleName, m.ad_module_id as moduleId from ad_table t, ad_module m, ad_package p, ad_column c where t.ad_package_id = p.ad_package_id and t.ad_table_id = c.ad_table_id and c.ad_module_id != p.ad_module_id and m.ad_module_id = c.ad_module_id and not exists (select 1 from ad_module_dbprefix dbp where instr(upper(c.name), 'EM_'||upper(dbp.name)||'_') = 1 and dbp.ad_module_id = c.ad_module_id) AND NOT EXISTS( SELECT 1 FROM AD_EXCEPTIONS WHERE TYPE='COLUMN' AND UPPER(NAME2)=UPPER(T.Tablename) AND UPPER(NAME1)=UPPER(c.Columnname)) and (2=2 and m.javapackage in ('%') or to_char('Y')=to_char(?)) order by 2,1 :org.postgresql.util.PSQLException: ERROR: could not determine which collation to use for string comparison
[WADValidation] Hint: Use the COLLATE clause to set the collation explicitly.
[WADValidation] 157716 [main] ERROR org.openbravo.wad.validation.WADValidatorData - SQL error in query: select i.name as objectName, (select max(name) from AD_Module_DBPrefix p where p.AD_Module_ID = i.AD_Module_ID) as expectedvalue from ad_auxiliarInput i, AD_Module m, AD_Tab t where i.ad_module_id != '0' and m.ad_module_id = i.ad_module_id and t.ad_tab_id = i.ad_tab_id and t.ad_module_id <> i.ad_module_id and not exists (select 1 from AD_Module_DBPrefix p where p.AD_Module_ID = i.AD_Module_ID and instr(upper(i.NAME), upper(p.name)||'_') = 1) and (m.javapackage in ('%') or to_char('Y')=to_char(?)) :org.postgresql.util.PSQLException: ERROR: could not determine which collation to use for string comparison
[WADValidation] Hint: Use the COLLATE clause to set the collation explicitly.
[WADValidation] 157746 [main] WARN org.openbravo.wad.validation.WADValidationResult - +++++++++++++++++++++++++++++++++++++++++++++++++++
[WADValidation] 157747 [main] WARN org.openbravo.wad.validation.WADValidationResult - Warnings for Validation type: SQL
[WADValidation] 157748 [main] WARN org.openbravo.wad.validation.WADValidationResult - +++++++++++++++++++++++++++++++++++++++++++++++++++
[WADValidation] 157749 [main] WARN org.openbravo.wad.validation.WADValidationResult - Error when executing query for validating model object: @CODE=0@ERROR: could not determine which collation to use for string comparison
[WADValidation] Hint: Use the COLLATE clause to set the collation explicitly.
[WADValidation] 157749 [main] WARN org.openbravo.wad.validation.WADValidationResult - Error when executing query for validating model object: @CODE=0@ERROR: could not determine which collation to use for string comparison
[WADValidation] Hint: Use the COLLATE clause to set the collation explicitly.

Steps To Reproduce

Install pg13 beta2
run install.source and check output of WADvalidation step

Tags

No tags attached.

Attached Files

Relationships [ Relation Graph ] [ Dependency Graph ]

blocks

feature request

0042449

closed

shuehner

support PostgreSQL 13

Notes
(0121774) shuehner (administrator) 2020-08-03 17:54	Note: Probably bug in pg13beta2 itself. Reported here for tracking it mostly.

(0121775) shuehner (administrator) 2020-08-03 18:13 edited on: 2020-08-04 15:44	Apparently same as reported here (postgresql development list) roughly a week ago: https://www.postgresql.org/message-id/20200721191606.GL5748%40telsasoft.com [^] Status: Fix apparently committed https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=cc4dd2a7af13b4759cd76074a932c8cf24e32bb2 [^] Fix should appear in beta3 (planned to come out on 2020-08-13)

(0122071) shuehner (administrator) 2020-08-14 15:11	PostgreSQL 13 beta3 fixed this problem. Closing with 'no change required'

Issue History
Date Modified	Username	Field	Change
2020-08-03 17:43	shuehner	New Issue
2020-08-03 17:43	shuehner	Assigned To	=> platform
2020-08-03 17:43	shuehner	Modules	=> Core
2020-08-03 17:43	shuehner	Triggers an Emergency Pack	=> No
2020-08-03 17:44	shuehner	Relationship added	blocks 0042449
2020-08-03 17:54	shuehner	Note Added: 0121774
2020-08-03 18:13	shuehner	Note Added: 0121775
2020-08-04 15:44	shuehner	Note Edited: 0121775	View Revisions
2020-08-14 15:11	shuehner	Note Added: 0122071
2020-08-14 15:11	shuehner	Status	new => closed
2020-08-14 15:11	shuehner	Resolution	open => no change required