Alias name restrictions is limited by 30 characters?

Posts   
 
    
guyronen
User
Posts: 26
Joined: 02-Mar-2021
# Posted on: 09-Jan-2022 19:22:21   

Hello I am getting an error from query generated by LLBLGen - LLBLGen version is 5.7.2

While its generating the query with automatic name on select fields like "LPA_L1"."F__2563764853" The field which replaced by automatic name is longer then 30 characters original name is : TaarichTchilatKisuyBekerenMaavira Is there any restrictions with field alias names ? Problem is that the new replaced name is not exists in my table Here is the query

Query:

SELECT "LPA_L1"."TRAP_NETUNEI_AMT_KUPA_MAVRA_ID" AS "TRAPNETUNEIAMTKUPAMAVRAID", "LPA_L1"."TRAP_PIRTEI_AMIT_OVER_ID" AS 
"TRAPPIRTEIAMITOVERID", "LPA_L1"."MAAMAD_AMIT_NOCHECHI" AS "MAAMADAMITNOCHECHI", "LPA_L1"."STATUS_AMIT_BAKUPA_HAMAAVIRA" AS 
"STATUSAMITBAKUPAHAMAAVIRA", "LPA_L1"."KOD_TEUR_KSAFIM" AS "KODTEURKSAFIM", "LPA_L1"."TAARICH_HITZTARFUT_AMIT" AS "TAARICHHITZTARFUTAMIT", 
"LPA_L1"."CHESHBON_O_POLISA_KUPA_MAAVIRA" AS "CHESHBONOPOLISAKUPAMAAVIRA", "LPA_L1"."TASHLUMIM_PTURIM" AS "TASHLUMIMPTURIM", 
"LPA_L1"."CREATION_DATE" AS "CREATIONDATE", "LPA_L1"."CREATION_USER" AS "CREATIONUSER", "LPA_L1"."UPDATE_DATE" AS "UPDATEDATE", 
"LPA_L1"."UPDATE_USER" AS "UPDATEUSER", "LPA_L1"."CREATION_LOGICAL_DATE" AS "CREATIONLOGICALDATE", "LPA_L1"."UPDATE_LOGICALDATE" AS 
"UPDATELOGICALDATE", "LPA_L1"."DELETED_DATE" AS "DELETEDDATE", "LPA_L1"."IS_DELETED" AS "ISDELETED", "LPA_L1"."F__340740911" AS "F__1552610955", 
"LPA_L1"."F__2563764853" AS "F__774702917" 
FROM "GAYA_B_PROD"."TRAP_NETUNEI_AMIT_KUPA_MAAVIRA" "LPA_L1"
 WHERE ( ( ( "LPA_L1"."TRAP_PIRTEI_AMIT_OVER_ID" = :P1))) AND ROWNUM >=  1

thank you , guy

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39588
Joined: 17-Aug-2003
# Posted on: 10-Jan-2022 09:49:33   

This issue was fixed in 5.7.5:

5.7.4 Oracle: Oracle 12.2C introduced longer identifier names, which break at runtime as they're converted to shorter names which don't match the table names. The DQE no longer clamps table/view/field names to 30 characters as it's unnecessary because the name is obtained from meta-data.

and

5.7.5 Oracle: A fixed made to v5.7.4 and 5.8.1 regarding name clamping caused an issue in edge cases when aliases were longer than 30 characters and targeting aliased fields also with names which were longer than 30 characters

So to fix it properly you need to upgrade to v5.7.5.

Frans Bouma | Lead developer LLBLGen Pro