Home » railML newsgroups » railml.common » Visualization: Proposal to move to a separate subschema
Re: Visualization: Proposal to move to a separate subschema [message #2531 is a reply to message #2530] Mon, 07 September 2020 14:29 Go to previous messageGo to previous message
Thomas Langkamm is currently offline  Thomas Langkamm
Messages: 25
Registered: April 2019
Junior Member
Dirk Bräuer wrote on Mon, 07 September 2020 10:38

However, I have some minor concerns:

> ...from a database/object-oriented standpoint (normalization), there
> should be no circular references.

This could even be a general thesis. But it is rather a theoretic, "nice to have" rule with not much practical background.[...]

I still would agree with your thesis but not as a strict rule, rather in a "recommendational", nice-to-have kind.
I agree. And if I may go off topic just a little bit: In some cases de-normalization (circular references are one example of that, redundant storage of data another) makes a lot of sense. Normalization often increases the complexity of the structures, increasing runtime and making them difficult to understand. And anybody who has been a victim of "overnormalization" -- in a database context it usually means waiting a very long time for some operation to finish, then calculating that it will take X million years to do so, and then ask the developers more or less politely what they have been thinking when designing this Razz -- will agree that normalization is more a guideline and not an axiom.

Having said this, in this specific I think normalization makes sense and has no drawbacks.
 
Read Message
Read Message
Read Message
Read Message
Previous Topic: [railML3] Handling changes between minor versions
Next Topic: Where to place a "comment" value?
Goto Forum:
  


Current Time: Sat Apr 20 05:42:16 CEST 2024