Re: [teiid-designer-dev] A new datatype
----- Original Message -----
Steve,
To be honest we haven't touched the built-in data-type definitions
for probably more than 5-6 years and I wasn't in charge of them back
then.
So there's a learning curve I have to jump on.
Designer's ".sdt" plugin contains both a built-in data-types .xsd &
.xmi files. Not sure yet how they are related and if both are used.
The XMI file does contain UUID's from the XSD file, or it could be
vice-versa.
It looks straight-forward to add the updated .xsd to a vdb and it will produce an
appropriate index file. I can use this to update the system vdb. I'll also put the
new xsd in the metadata module with the system vdb for reference.
However the .xmi file does not appear to be recognized by either old (554) or new versions
of designer. Can you determine if the .xmi file is in use?
So as a minimum you are correct, adding the "varbinary" type to
builtin-types.xsd is the place to start.
And I don't know the answer to "do we index enterprise datatype
information on a per vdb basis?
The answer is indeed yes, which is what I was expecting. The long run question is then
what additional information is needed to make those entries truly extensible datatypes
rather than just being reduced to their base runtime type. That is much too big to do for
8, so for now we'll just look at adding more built-in types.
Barry
From: "Steven Hawkins" <shawkins(a)redhat.com>
To: "teiid-designer-dev" <teiid-designer-dev(a)lists.jboss.org>
Sent: Wednesday, January 18, 2012 11:00:12 AM
Subject: Re: [teiid-designer-dev] A new datatype
A follow-up question. The datatypes index we use in the system vdb
looks like it was generated from the builtin-types.xsd. To add a new
type, do I need to modify that xsd and in what version of designer
would I then generate the appropriate index file? Related to that,
do we index enterprise datatype information on a per vdb basis?
----- Original Message -----
> Hello all,
>
> What would be the impact in designer for adding a new type?
> https://issues.jboss.org/browse/TEIID-1834 could be achieved by
> adding a varbinary type. At the very least on the teiid side we'd
> update the DatatypeManager, the system vdb, and our type logic. But
> I'm not clear what impact there would be design time. Based upon
> the ease/difficulty of this we'll also be able to evaluate when it
> makes sense to add array type handling.
>
> Steve
_______________________________________________
teiid-designer-dev mailing list
teiid-designer-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/teiid-designer-dev
_______________________________________________
teiid-designer-dev mailing list
teiid-designer-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/teiid-designer-dev