On Mar 26, 2010, at 2:24 PM, Ramesh Reddy wrote:
I am calling it "Preview API" for now. Consider that if
this API has
following methods ( !!!these will not be the methods!!!) for
illustration purpose
createVDB(vdbName);
addModel(vdbName, modelName, indexContents, sourceName/jndi)
deleteModel(vdbName, modelName)
How would we update a model?
Actually for your workspace, no need to do this vdb or model or all
models in a preview query any more. When a model changes/previewed then
you can choose to update *only* the changed models and then issue a
query.
I was trying to reduce the number of models we sent over the wire, assuming several in the
workspace would never be previewed during a session, but maybe your approach, or perhaps a
per-project approach, is better just to reduce the number of communications required.
no to this. No really need hidden; just keep what you have now.
Create
sudo "preview" vdb on server, just update the models as you go. If not,
keep "preview" vdb per/project to minimize size of unnecessary models in
the Teiid.
"No" to what - the naming? If so, yes, we'll name them. But we'd still
want the preview VDBs hidden from the user.
Thanks,
JPAV