Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
lalbatros
Yak Posting Veteran
69 Posts |
 Posted - 2008-06-09 : 09:43:19
|
| Hello,I have encoutered many different unsatisfactory solutions for a simple db.It is so simple that I thought it might well be a very simple example for an object database.But I am sure a relational expert will have some useful comments and maybe a relational representation.The problem is essentially: building a table or a view of material movements in an industrial compagny.Considering the processes involved in my industry, there are many different ways of defining or measuring a "material movement".Some could be directly measured in tons/day. (like trucks movements)Other could be based on several data and some calculation methods. (like geometrical data or calibrations)Some might even need historical data (like when silos are involved).It is useful to store not only the end-result, the movements in tons/day, but also the raw data needed to calculate it. At least this can allow some corrections or some analysis.Therefore, it seems quite natural to consider the different kinds of movements as different kinds of objects and to build this database on an objected-oriented basis, a very simple one.I am equally interrested on the two approach to store these information: object or relational.The relational model, however, would simplify my life since I would not need to install and learn something new to me. |
|
|
|
|
|
objectDb without objectDb, polymorphism