Re: [teiid-designer-dev] other model types
On Mar 25, 2010, at 5:00 PM, Steven Hawkins wrote:
Now we have:
Barry - include them all
and
John - include them only if there is some ui reason
So they should be included then, because Designer is a ui and used to use those values
for something?
Just to make sure my assumptions are correct, if there is additional values you guys want
to track, then they will be set as properties on the model in the vdb.xml rather than
going into a separate model manifest (such as the old entries for model, path, uuid, or
update time)? And if that is the case then it seems like you will want model entries in
the vdb.xml for these other model types.
Yes, the property support is a good point. Unless Barry knows of a specific reason why
the types are anything more than just a UI concern, it seems like we'd just use the
generic property name-value pair support in the vdb.xml to support anything specific to
the UI. Why would you guys support UI-only model types in the main schema if they're
not useful in the runtime?
JPAV