Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » EMF "Technology" (Ecore Tools, EMFatic, etc)  » Teneo @Index support
Teneo @Index support [message #87056] Thu, 21 June 2007 19:27 Go to next message
Jason Henriksen is currently offline Jason HenriksenFriend
Messages: 231
Registered: July 2009
Senior Member
My DBA wont allow me to use teneo to drive DB management unless I can
establish arbitrary indexes on columns. (This is completely reasonable
since we will be putting 52 million consumer records in to it)

It seems that this just isn't supported, but hopefully I just haven't found
the right way to do it.

<xsd:element name="SSN" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="teneo.jpa">
@Column(name="SSN",length="9")
@Index(name="IDX_CMR36013")
</xsd:appinfo>
<xsd:documentation>Social Security Number</xsd:documentation>
</xsd:annotation>
</xsd:element>

I've also tried:

<xsd:complexType name="Consumer">
<xsd:annotation><xsd:appinfo source="teneo.jpa">
@Table(
name="CMR3601T"
uniqueConstraints = { @UniqueConstraint(columnNames={"CONSUMER_SK"}),

@UniqueConstraint(columnNames={"CONSUMER_SK", "DATE_OF_BIRTH"})}
indexes = {
@Index(name="CMR36011", columnNames={"CONSUMER_SK"}),
@Index(name="CMR36016",
columnNames={"CONSUMER_SK","DATE_OF_BIRTH"}),
@Index(name="CMR36013", columnNames={"SSN"}),
@Index(name="CMR36014", columnNames={"DATE_OF_BIRTH"}),
@Index(name="CMR36015", columnNames={"CONSUMER_ID"})
}
)
</xsd:appinfo></xsd:annotation>
...
</xsd:complexType>

The unique constraints seem to work fine, but the indexes cause an
exception. Any help getting this work would be greatly appreciated. If it
isn't supported, is there anything I could do to help get it working?

Thanks very much,

Jason Henriksen
Re: Teneo @Index support [message #87071 is a reply to message #87056] Thu, 21 June 2007 22:12 Go to previous messageGo to next message
Martin Taal is currently offline Martin TaalFriend
Messages: 5468
Registered: July 2009
Senior Member
I have included this a few weeks ago in Teneo and have used it at a customer. So it's there but it
will be some time (a few weeks) before I can release a new build.

gr. Martin

Jason Henriksen wrote:
> My DBA wont allow me to use teneo to drive DB management unless I can
> establish arbitrary indexes on columns. (This is completely reasonable
> since we will be putting 52 million consumer records in to it)
>
> It seems that this just isn't supported, but hopefully I just haven't found
> the right way to do it.
>
> <xsd:element name="SSN" type="xsd:string">
> <xsd:annotation>
> <xsd:appinfo source="teneo.jpa">
> @Column(name="SSN",length="9")
> @Index(name="IDX_CMR36013")
> </xsd:appinfo>
> <xsd:documentation>Social Security Number</xsd:documentation>
> </xsd:annotation>
> </xsd:element>
>
> I've also tried:
>
> <xsd:complexType name="Consumer">
> <xsd:annotation><xsd:appinfo source="teneo.jpa">
> @Table(
> name="CMR3601T"
> uniqueConstraints = { @UniqueConstraint(columnNames={"CONSUMER_SK"}),
>
> @UniqueConstraint(columnNames={"CONSUMER_SK", "DATE_OF_BIRTH"})}
> indexes = {
> @Index(name="CMR36011", columnNames={"CONSUMER_SK"}),
> @Index(name="CMR36016",
> columnNames={"CONSUMER_SK","DATE_OF_BIRTH"}),
> @Index(name="CMR36013", columnNames={"SSN"}),
> @Index(name="CMR36014", columnNames={"DATE_OF_BIRTH"}),
> @Index(name="CMR36015", columnNames={"CONSUMER_ID"})
> }
> )
> </xsd:appinfo></xsd:annotation>
> ...
> </xsd:complexType>
>
> The unique constraints seem to work fine, but the indexes cause an
> exception. Any help getting this work would be greatly appreciated. If it
> isn't supported, is there anything I could do to help get it working?
>
> Thanks very much,
>
> Jason Henriksen
>
>


--

With Regards, Martin Taal

Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal@springsite.com - mtaal@elver.org
Web: www.springsite.com - www.elver.org
Re: Teneo @Index support [message #87086 is a reply to message #87071] Thu, 21 June 2007 23:09 Go to previous message
Jason Henriksen is currently offline Jason HenriksenFriend
Messages: 231
Registered: July 2009
Senior Member
Excellent. I'll definitely be excited to get that deployed.

Thank you for all of your work on this project,

Jason

"Martin Taal" <mtaal@elver.org> wrote in message
news:f5et4u$4jp$1@build.eclipse.org...
> I have included this a few weeks ago in Teneo and have used it at a
customer. So it's there but it
> will be some time (a few weeks) before I can release a new build.
>
> gr. Martin
>
> Jason Henriksen wrote:
> > My DBA wont allow me to use teneo to drive DB management unless I can
> > establish arbitrary indexes on columns. (This is completely reasonable
> > since we will be putting 52 million consumer records in to it)
> >
> > It seems that this just isn't supported, but hopefully I just haven't
found
> > the right way to do it.
> >
> > <xsd:element name="SSN" type="xsd:string">
> > <xsd:annotation>
> > <xsd:appinfo source="teneo.jpa">
> > @Column(name="SSN",length="9")
> > @Index(name="IDX_CMR36013")
> > </xsd:appinfo>
> > <xsd:documentation>Social Security Number</xsd:documentation>
> > </xsd:annotation>
> > </xsd:element>
> >
> > I've also tried:
> >
> > <xsd:complexType name="Consumer">
> > <xsd:annotation><xsd:appinfo source="teneo.jpa">
> > @Table(
> > name="CMR3601T"
> > uniqueConstraints = {
@UniqueConstraint(columnNames={"CONSUMER_SK"}),
> >
> > @UniqueConstraint(columnNames={"CONSUMER_SK", "DATE_OF_BIRTH"})}
> > indexes = {
> > @Index(name="CMR36011", columnNames={"CONSUMER_SK"}),
> > @Index(name="CMR36016",
> > columnNames={"CONSUMER_SK","DATE_OF_BIRTH"}),
> > @Index(name="CMR36013", columnNames={"SSN"}),
> > @Index(name="CMR36014", columnNames={"DATE_OF_BIRTH"}),
> > @Index(name="CMR36015", columnNames={"CONSUMER_ID"})
> > }
> > )
> > </xsd:appinfo></xsd:annotation>
> > ...
> > </xsd:complexType>
> >
> > The unique constraints seem to work fine, but the indexes cause an
> > exception. Any help getting this work would be greatly appreciated. If
it
> > isn't supported, is there anything I could do to help get it working?
> >
> > Thanks very much,
> >
> > Jason Henriksen
> >
> >
>
>
> --
>
> With Regards, Martin Taal
>
> Springsite/Elver.org
> Office: Hardwareweg 4, 3821 BV Amersfoort
> Postal: Nassaulaan 7, 3941 EC Doorn
> The Netherlands
> Tel: +31 (0)84 420 2397
> Fax: +31 (0)84 225 9307
> Mail: mtaal@springsite.com - mtaal@elver.org
> Web: www.springsite.com - www.elver.org
Re: Teneo @Index support [message #607036 is a reply to message #87056] Thu, 21 June 2007 22:12 Go to previous message
Martin Taal is currently offline Martin TaalFriend
Messages: 5468
Registered: July 2009
Senior Member
I have included this a few weeks ago in Teneo and have used it at a customer. So it's there but it
will be some time (a few weeks) before I can release a new build.

gr. Martin

Jason Henriksen wrote:
> My DBA wont allow me to use teneo to drive DB management unless I can
> establish arbitrary indexes on columns. (This is completely reasonable
> since we will be putting 52 million consumer records in to it)
>
> It seems that this just isn't supported, but hopefully I just haven't found
> the right way to do it.
>
> <xsd:element name="SSN" type="xsd:string">
> <xsd:annotation>
> <xsd:appinfo source="teneo.jpa">
> @Column(name="SSN",length="9")
> @Index(name="IDX_CMR36013")
> </xsd:appinfo>
> <xsd:documentation>Social Security Number</xsd:documentation>
> </xsd:annotation>
> </xsd:element>
>
> I've also tried:
>
> <xsd:complexType name="Consumer">
> <xsd:annotation><xsd:appinfo source="teneo.jpa">
> @Table(
> name="CMR3601T"
> uniqueConstraints = { @UniqueConstraint(columnNames={"CONSUMER_SK"}),
>
> @UniqueConstraint(columnNames={"CONSUMER_SK", "DATE_OF_BIRTH"})}
> indexes = {
> @Index(name="CMR36011", columnNames={"CONSUMER_SK"}),
> @Index(name="CMR36016",
> columnNames={"CONSUMER_SK","DATE_OF_BIRTH"}),
> @Index(name="CMR36013", columnNames={"SSN"}),
> @Index(name="CMR36014", columnNames={"DATE_OF_BIRTH"}),
> @Index(name="CMR36015", columnNames={"CONSUMER_ID"})
> }
> )
> </xsd:appinfo></xsd:annotation>
> ...
> </xsd:complexType>
>
> The unique constraints seem to work fine, but the indexes cause an
> exception. Any help getting this work would be greatly appreciated. If it
> isn't supported, is there anything I could do to help get it working?
>
> Thanks very much,
>
> Jason Henriksen
>
>


--

With Regards, Martin Taal

Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal@springsite.com - mtaal@elver.org
Web: www.springsite.com - www.elver.org
Re: Teneo @Index support [message #607037 is a reply to message #87071] Thu, 21 June 2007 23:09 Go to previous message
Jason Henriksen is currently offline Jason HenriksenFriend
Messages: 231
Registered: July 2009
Senior Member
Excellent. I'll definitely be excited to get that deployed.

Thank you for all of your work on this project,

Jason

"Martin Taal" <mtaal@elver.org> wrote in message
news:f5et4u$4jp$1@build.eclipse.org...
> I have included this a few weeks ago in Teneo and have used it at a
customer. So it's there but it
> will be some time (a few weeks) before I can release a new build.
>
> gr. Martin
>
> Jason Henriksen wrote:
> > My DBA wont allow me to use teneo to drive DB management unless I can
> > establish arbitrary indexes on columns. (This is completely reasonable
> > since we will be putting 52 million consumer records in to it)
> >
> > It seems that this just isn't supported, but hopefully I just haven't
found
> > the right way to do it.
> >
> > <xsd:element name="SSN" type="xsd:string">
> > <xsd:annotation>
> > <xsd:appinfo source="teneo.jpa">
> > @Column(name="SSN",length="9")
> > @Index(name="IDX_CMR36013")
> > </xsd:appinfo>
> > <xsd:documentation>Social Security Number</xsd:documentation>
> > </xsd:annotation>
> > </xsd:element>
> >
> > I've also tried:
> >
> > <xsd:complexType name="Consumer">
> > <xsd:annotation><xsd:appinfo source="teneo.jpa">
> > @Table(
> > name="CMR3601T"
> > uniqueConstraints = {
@UniqueConstraint(columnNames={"CONSUMER_SK"}),
> >
> > @UniqueConstraint(columnNames={"CONSUMER_SK", "DATE_OF_BIRTH"})}
> > indexes = {
> > @Index(name="CMR36011", columnNames={"CONSUMER_SK"}),
> > @Index(name="CMR36016",
> > columnNames={"CONSUMER_SK","DATE_OF_BIRTH"}),
> > @Index(name="CMR36013", columnNames={"SSN"}),
> > @Index(name="CMR36014", columnNames={"DATE_OF_BIRTH"}),
> > @Index(name="CMR36015", columnNames={"CONSUMER_ID"})
> > }
> > )
> > </xsd:appinfo></xsd:annotation>
> > ...
> > </xsd:complexType>
> >
> > The unique constraints seem to work fine, but the indexes cause an
> > exception. Any help getting this work would be greatly appreciated. If
it
> > isn't supported, is there anything I could do to help get it working?
> >
> > Thanks very much,
> >
> > Jason Henriksen
> >
> >
>
>
> --
>
> With Regards, Martin Taal
>
> Springsite/Elver.org
> Office: Hardwareweg 4, 3821 BV Amersfoort
> Postal: Nassaulaan 7, 3941 EC Doorn
> The Netherlands
> Tel: +31 (0)84 420 2397
> Fax: +31 (0)84 225 9307
> Mail: mtaal@springsite.com - mtaal@elver.org
> Web: www.springsite.com - www.elver.org
Previous Topic:Teneo @Index support
Next Topic:[EMF Compare] text compare instead of emf compare
Goto Forum:
  


Current Time: Thu Jan 21 06:12:24 GMT 2021

Powered by FUDForum. Page generated in 0.01460 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top