BODI and automatic use of table alias

Question

I have a problem with BODI's automatic use of table alias as the same as the table name, when the table name is a reserved word.
I'm reading from an Informix database, where I've got a table named aggregate. This is a reserved word and gives me problems when BODI is generating the optimized SQL for my select statement.
The generated SQl would look like this (simplified):
SELECT  aggregate.aggr_id
FROM informix.aggregate aggregate
This will fail (I'm using an odbc connection), due to syntax error.
Running this within Aqua Studio will also fail. Changing the table alias to aggr will work fine.
My question is how I can prevent or owerride BODI's use of aggregate as the table alias in this case.

Answer 1

Have you tried the Templates?
1. Select Tools > General Options
2. Expand Naming Standards and select Templates
3. Set the template structure you want to use. I used abbreviation (table) or short name(entity) here. i.e use the "Add Variable button to see the options available and add as required. In this instance I'd suggest using the abbreviation e.g. for the primary key I have {table abbr}_PK. Note that you can use "substr" here too.
4. Apply the change and go to the model.
Now these template work in 3 different ways.
1. When transforming or forward engineering the logical to relational models, the templates are applied to the key creation.
2. In the Relational diagram when drawing new relationships between tables or adding new constraints.
3. After the fact, if you apply the templates. Either 1 at a time or globally.
a. To update a single table: To do this select any table and invoke the property palette. Select the Naming Rules button. Check the rules you want to update and click OK. The templates are now applied to your table, renaming the keys.
b. To update multiple tables, select the relational model mode int he Browser, right-click for the context menu and select "Apply Naming Standards" This will update all the items in the model using the template structure set. Please note, regrettably this last (3b), does not work in the latest patch release, but if you are on the initial production release, then the tables are all updated. This has been bugged and fixed and so will be rectified in the next release.
Regards
Sue