Dear Mehrotra,
I think I got your point, when using unstructured nodes I loose all
benefits of, for example, an hierarchical structure. However I still don't
understand the part regarding the versions, and how the use of
unstructured, or loosely structured nodes, will help my problem. Here my
original question:
> *if a node is unstructured i can add or remove any property from node
without any problem, but i can't do that to its versions right? If i need
to apply a calculated value to each version, so that i don't have to make
that calculation any time i retrieve that version information, how can i do
that?*

how can i update those information without having to recreate the whole
version history again?

Marco.


On Wed, Aug 2, 2017 at 8:55 AM, Chetan Mehrotra <chetan.mehro...@gmail.com>
wrote:

> > it is preferable to not create custom node types, because typically the
> business requirements are not understood enough
>
> Nodetypes are helpful as "content annotation" and allow repository to
> provide better performance by relying on them for indexing,
> observation, bundling etc. So may be better to say avoid nodetypes
> with restrictive definition. However do create new nodetype (or
> mixins) to mark the domain objects in your application content.
>
> Chetan Mehrotra
>



-- 

marco piovesanA
Enterprise Application



*ESTECO* | EXPLORE DESIGN PERFECTION

AREA Science Park, Padriciano 99 - 34149 Trieste - ITALY
Phone: +39 040 3755548 - Fax: +39 040 3755549
[Website] <http://www.esteco.com> | [Twitter]
<https://twitter.com/esteco_mF> | [Facebook]
<https://www.facebook.com/esteco.spa> | [Linkedin]
<https://www.linkedin.com/company/748217>
Pursuant to Legislative Decree No. 196/2003, you are hereby informed that
this message contains confidential information intended only for the use of
the addressee. If you are not the addressee, and have received this message
by mistake, please delete it and immediately notify us. You may not copy or
disseminate this message to anyone. Thank you. Please consider the
environment before printing this email.

Reply via email to