CapableObjects Forums / ECO / General discussions / Anyone ever ask for or want "Indexed Attributes"? / Latest Posts

RE: Anyone ever ask for or want "Indexed Attributes"?

AndyG — Mon, 15 Mar 2010 04:10:19 GMT

Ha! You guys must be reading minds ;-) We've just been discussing the need for extra indexes last week. And yes it would be great to have a design time feature in ECO to create these :)

Further to this, I know it's been mentioned recently in another thread... Is there any chance of posting a road map for develpment? We're currently looking for a good reason to upgrade from ECO IV and at present there seems to be little benefit in terms of must have features. (as opposed to a few nice things).

Were any descisions or comitments made after the not so long ago poll on most desired fixes and features for ECO? Specifically for us: is there any news on fixing PS queries for Versioned classes? It's really getting time where our deployed ECO project needs this kind of optimisation, and with indexing, maybe we even get to zoom again!...

Andy

RE: Anyone ever ask for or want "Indexed Attributes"?

OZh — Mon, 15 Mar 2010 03:09:47 GMT

[b]I'd vote for it too.[/b]

My model has many associations like this:

Class1 -- (1) ---------------- (*) -- Class2

With Class2 having month : DateTime attribute. And I often search linearly among associated Class2 instances for a one with particular month. So it would be nice to have a qualified association with O(1) navigation time.

Class1 -- (1) ---------------- [month : DateTime] (1) -- Class2

RE: Anyone ever ask for or want "Indexed Attributes"?

Kristijan Deberni — Thu, 11 Mar 2010 10:30:09 GMT

That would be great.

RE: Anyone ever ask for or want "Indexed Attributes"?

wangwei.njcn — Wed, 10 Mar 2010 09:57:47 GMT

Yes ,I want to them;:D

RE: Anyone ever ask for or want "Indexed Attributes"?

RickWeyrauch — Fri, 05 Mar 2010 13:40:28 GMT

I was actually thinking the exact same thing. A place where I can define a bunch of SQL that runs after the Eco Create Database. That would have helped me in another project that had some blob fields for storing large binary files. I wanted to place those fields in a seperate FILEGROUP. Eco does not provide a way to set this, but the ability to run a script after Create would have done the trick. Which is exactly what I did - I just had to do it manually via a query window.

I still want to ability to tell Eco to make a hash lookup for a given field in memory if I know my users will be thrashing on that field via searches.

RE: Anyone ever ask for or want "Indexed Attributes"?

Peter Morris — Fri, 05 Mar 2010 09:41:33 GMT

[quote][b]RickWeyrauch (2010-03-03)[/b][hr]I had something come up where I wanted to database to do the work for me and so I rattled off a OclPS that did the trick, lickity-split! Then I started thinking.... I suppose I should go add an index to the database on the columns I am cranking against to speed things up. Well, that got me thinking.... shouldn't there be a way to specify that an Attribute is an Indexed Attribute? It could have 2 effects, add the necessary index to the database table and Eco could also make some type of memory hash too.

In my current case, I really want the index based on 2 Attributes but I figure that might be a lot more difficult to do.[/quote]

I think that a hook into the DB generation/evolve would be useful, that way I could check for tagged values like "Pete.CreateIndex" and create an index, or add prohibit-delete referential integrity when Eco.IsConstrained=True.

RE: Anyone ever ask for or want "Indexed Attributes"?

Alex Vedmedenko — Thu, 04 Mar 2010 12:32:49 GMT

there is interface for such type of association, and there feature request already 2 years old for it. :)

RE: Anyone ever ask for or want "Indexed Attributes"?

brian — Wed, 03 Mar 2010 22:46:31 GMT

I want them :)

RE: Anyone ever ask for or want "Indexed Attributes"?

RickWeyrauch — Wed, 03 Mar 2010 13:26:07 GMT

Well, get on with it! I want it both ways ;)

RE: Anyone ever ask for or want "Indexed Attributes"?

Jonas Hogstrom — Wed, 03 Mar 2010 11:46:24 GMT

In Bold, there was (is) a feature called qualified relations that allowed you to query a multilink like this:

Model snippet:

[code]
-------- -------------------------
| Bank | (1) ---------- (*) [AccountNumber] | Account |
-------- | --------------------- |
| AccountNumber: string |
-------------------------
[/code]
Ocl:
aBank.Accounts['123123']

this would return the account with accountnumber.

This was maintained only in memory with a hash-index that was automatically updated using subscriptions when the account number of an object was changed. There is no such feature in ECO... I've been wanting to add support for adding automatic database indices based on properties in the model for a long time, but never come around to it.

Anyone ever ask for or want "Indexed Attributes"?

RickWeyrauch — Wed, 03 Mar 2010 03:43:21 GMT

I had something come up where I wanted to database to do the work for me and so I rattled off a OclPS that did the trick, lickity-split! Then I started thinking.... I suppose I should go add an index to the database on the columns I am cranking against to speed things up. Well, that got me thinking.... shouldn't there be a way to specify that an Attribute is an Indexed Attribute? It could have 2 effects, add the necessary index to the database table and Eco could also make some type of memory hash too.

In my current case, I really want the index based on 2 Attributes but I figure that might be a lot more difficult to do.