> The reason why I say science/engineering applications are better > suited for OO databases is that they usually have complex > relationships between their classes and their is very little need to > query on attributes other than those used for their relationships. > Business applications usually require querying on a large percentage > of their attributes and thus better suited for relation DBs. Like I > said in an early post these are just stereotypes as some business apps > are better suited using an OO DB and likewise some science apps are > better suited for relational DB.
That makes sense thinking a bit about it. Thanks for the interesting read. > Hopefully this brief explanations clears things up a little. To give > an explanation that covers this topic fully would likely require > coming up with 2 examples (one good for OO and one good for > relational) and then code each one using both database types and thus > create 4 applications. Once this is done a comparison of the 2 > applications for each example could be done. This would clearly show > the costs that are involved with selecting the wrong type of database > for the job. Unfortunately I just don't have the free time to do > this. Understandable, though it would certainly be interesting to see something like that down the road once ( or if ) TG has OODB support! Thanks Iain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
