How to restrict the generated constraint name with Model Driven Development

Question

Hello
I have a database that has tables INSTRUMENT and EXCHANGE. There has to be a foreign key field called primaryExchange inside INSTRUMENT table that points to the ID of EXCHANGE table. In my fml file, my tables are called Instrument and Exchange. When I create this relation between the two tables in the model and deploy it to LCDS, it tries to create a FK constraint by the name of "FK_Instrument_primaryExchange_TO_Exchage" which fails with ORA-00972 -  Identifier is too long. Obviously the generated FK name is more than 30 chars and hence the oracle erorr. The only way to resolve this is to reduce the name of the table/field in the fml file while keeping the database table/field name intact. So the FK might be called FK_Instr_primExch_TO_Exch and which will work but the problem is that in the fml model file, I am loosing the meaningful names of the tables and thus the data services that are generated have truncated names. For this particular example, the truncated name might still be okay but in a large database, it is causing much grief. I would really prefer decent descriptive names for table like MarketOrder instead of MO. Pls advise how I can customize the generated constraint name while keeping the tables names still informative.
Now I edit my DB tables to have a field called ID which is unique to that table but while deploying I get hibernate and fiber exceptions :-
2011-03-10 16:30:44,042 INFO  [STDOUT] (http-0.0.0.0-8180-1) [UlltraWebServer]Exception trying to build hibernate's session factory: org.hibernate.MappingException: Repeated column in mapping for entity: UlltraWebServer.package4.Client column: ID (should be mapped with insert="false" update="false")
2011-03-10 16:30:44,116 INFO  [STDOUT] (http-0.0.0.0-8180-1) [UlltraWebServer]Error instantiating application scoped instance of type 'fiber.data.assemblers.FiberAssembler' for destination 'UlltraWebServer.Holiday'.
org.hibernate.MappingException: Repeated column in mapping for entity: UlltraWebServer.package4.Client column: ID (should be mapped with insert="false" update="false")
2011-03-10 16:30:44,229 INFO  [STDOUT] (http-0.0.0.0-8180-1) [UlltraWebServer]Exception trying to build hibernate's session factory: org.hibernate.MappingException: Repeated column in mapping for entity: UlltraWebServer.package4.Client column: ID (should be mapped with insert="false" update="false")
The above suggests that it does not like the same name for the fields in multiple tables, they all have to be unique like Holiday.holidayID, Client.clientID etc which causes the above constraint length violation issue..
thanks

Answer 1

You should be able to achieve what you want with an explicit criteria filter on your entity.
In the Modeler Design view, select your entity and add a filter. You'll see that there is a an "Order By" field in the Properties view.
Enter the value you want there and then save and redeploy your model. When you don't enter anything in the "Criteria" field, you create a getAll fill.
Here's an example of an entity created with this type of filter; it is sorted by price in ascending order:
<entity name="Product" persistent="true">
  <annotation name="ServerProperties" ServerType="LCDS"/>
  <annotation name="DMS" Table="PRODUCT"/>
  <annotation name="RDS" introspectedColumns="PRODUCTID,DESCRIPTION,PRICE,PRODUCTNAME"/>
  <annotation name="VisualModeler" width="115" height="110" x="364" y="203"/>
  <id name="productid" type="integer">
  <annotation name="DMS" ColumnName="PRODUCTID"/>
  </id>
  <property name="description" type="string" length="255">
  <annotation name="DMS" ColumnName="DESCRIPTION"/>
  </property>
  <property name="price" type="float">
  <annotation name="DMS" ColumnName="PRICE"/>
  </property>
  <property name="productname" type="string" length="255">
  <annotation name="DMS" ColumnName="PRODUCTNAME"/>
  </property>
  <filter name="MyFill" order="price ASC"/>
  </entity>