ASPECT or attribute addition is better option?

We have a requirement that we need to add additional attribute in existing object type that has millions of data. Some expert has suggested that if you add additional attribute then it will take lots of space in data base (Oracle in my case) for existing objects as well. So instead of adding new attribute create an ASPECT and add the attribute value in this aspect.

My question is that which one will be better option.

1. Adding new attribute?

2. Adding an aspect? This case also it will create a table in database with new aspect objects.

Please help me on this.

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

msroth

Based on what little you have shared about the environment and business requirements, I think I'd go with adding an attribute to the object model. It's simpler to implement.

All comments

bacham2

I don't think that the database space should be considered here. Instead, you should focus on the business requirements. If this attribute is not going to be used across several types all over your type hierarchy, then just add it as a normal attribute. Furthermore, if you use an aspect, this will impact how you can access this attribute in DQL and also programmatically or through whichever client application you use. Therefore, you probably don't want to handle this attribute any differently than your other attributes. Finally, if your attribute is repeating, adding it should not use much more space since it will only contain NULL values which do not consume space. If it's single and a string, than it will take some space but there is no way around that.

SantoshJha

Thanks for your reply. I am also thinking the same. But the data model designer is preferring aspect on top of attribute addition because of 50 millions of existing data.

msroth

Even with an aspect you are adding 50 million "somethings" to the database (aspects store their metadata in the database too), unless the aspect would only be applied to a select few of the objects. But even so, a NULL attribute doesn't consume any space. Based upon what you have said here, I think @bacham2 gave you the right advice with the right justifications.

SantoshJha

Thanks to both of you....Here my requirement is...We have existing object type that contains more that 50 millions of data. The same object type shared with different users/clients. One new user is going to access this object type in future with one extra parameter. To add this parameter, which solution would be better....1)ASPECT or 2) Attribute addition.

Please remember that only one user will use this attribute/ASPECT. This attribute/Aspect will not be used by other users as its not their requirement.

Now it we use Aspect then where the benefit is? Is in database side? If not then is it useful to go with attribute addition?

Now please suggest.

msroth

Based on what little you have shared about the environment and business requirements, I think I'd go with adding an attribute to the object model. It's simpler to implement.

Alvaro_de_Andres

If you use an aspect you'll have to modify every application your user uses to be aware of aspects, as these are not handled automatically as normal attributes are. Just for that reason you should discard using aspects unless it a clear scenario for using aspects (and if you have doubts, it is not )

SantoshJha

Hi Alvaro,

In my condition we need to modify only one place if we go for Aspect. So are you suggesting to use Aspect?

Alvaro_de_Andres

I'm just giving you something to consider. I wouldn't use aspects over attributes unless: it's a clear scenario for an aspect or it is impossible to add an attribute (ie: extending dm_document).

Otherwise, aspects involve too much complexity and problems (modify applications, future applications, migrations, etc)

lastnitescurry

A) have you considered using an existing but unused attribute? E.g. title, subject, keywords, authors, log_entry, a_is template, a_status,.....

have you considered relationships which webtop does support.

C) Curious, as to business process that requires one person to find an update one or more of 50 million files