-
1. Re: Storing per-model-instance data
rareddy Mar 19, 2014 1:54 PM (in response to tom9729)Tom,
This is where the "extension metadata" properties come into picture. These are same as ones you define in OPTIONS clause if you are defining DDL for your schema on model. So in effect you can define these properties in your translator, and set those properties on a table, column, procedure and/key where you see fit. Then these properties become part of your schema definition and will be send back to you along with user query to the translator. During the execution you can read them back from metadata object and take further decisions on the query planning and execution.
HTH
Ramesh..
-
2. Re: Storing per-model-instance data
tom9729 Mar 19, 2014 4:41 PM (in response to rareddy)Thanks Ramesh!
I ended up using setProperty() on Table/Column to do this programmatically (as opposed to DDL/DDL-FILE). This seems to work.
Is there a note on this in the documentation?
Tom
-
3. Re: Storing per-model-instance data
rareddy Mar 19, 2014 4:59 PM (in response to tom9729)Tom,
Yes, I do mean you need to use the "setProperty" on the metadata object of schema elements of table, column etc. I gave DDL as reference to how this was used in DDL. I thought there was note in the documentation but I could not find any, will add. IMO the Developer's Guide really needs to some face lift to make it more consumable using a simple example. May be you can contribute to the doc?
Thanks
Ramesh..
-
4. Re: Storing per-model-instance data
tom9729 Mar 19, 2014 5:37 PM (in response to rareddy)There are a couple of places that could use a little more detail. I've been leaving comments and submitting a few edits. I'll see what I can do.
Thanks,
Tom