codek
10-31-2008, 04:52 AM
Hi,
We noticed something interesting last night with metadata.
When a query is generated it creates sql like so
select * from BV_TABLE_A TableName
Where TableName is the name of the business table.
However, it uses the SERVER locale to lookup the alias for BV_TABLE_A. So if your server locale doesnt match your metadata locale then it wont use the nice name for the alias, it will use the ID
The problem then is that the ID's often dont work because they tend to be very long, and the DB (oracle) rejects them as being identifier too long.
So thats one to look out for! I think it's a bug really because there's no need to use locale specific names here, it could just use TABLEA, TABLEB like it does with the columns where it uses COL1, COL2 etc. I'm glad we spotted it was the locale difference otherwise this could have been an absolute mare to work out.
This is 1.7GA, i know things have changed with long identifiers in 2.0 a little, but not sure if this "issue" still exists.
I havent tested yet, but i think the workaround is to set the locale-language and locale-country in the web.xml. At the moment we have a default web.xml which has these blank, so i assume thats why it inherits from the OS.
Hey ho...
Dan
We noticed something interesting last night with metadata.
When a query is generated it creates sql like so
select * from BV_TABLE_A TableName
Where TableName is the name of the business table.
However, it uses the SERVER locale to lookup the alias for BV_TABLE_A. So if your server locale doesnt match your metadata locale then it wont use the nice name for the alias, it will use the ID
The problem then is that the ID's often dont work because they tend to be very long, and the DB (oracle) rejects them as being identifier too long.
So thats one to look out for! I think it's a bug really because there's no need to use locale specific names here, it could just use TABLEA, TABLEB like it does with the columns where it uses COL1, COL2 etc. I'm glad we spotted it was the locale difference otherwise this could have been an absolute mare to work out.
This is 1.7GA, i know things have changed with long identifiers in 2.0 a little, but not sure if this "issue" still exists.
I havent tested yet, but i think the workaround is to set the locale-language and locale-country in the web.xml. At the moment we have a default web.xml which has these blank, so i assume thats why it inherits from the OS.
Hey ho...
Dan