On Apr 26, 2007, at 9:06 AM, Adrian Crum wrote:
David,Thank you very much for the reply! I looked at workeffort again and it's too "heavy" for what I have in mind. I see the calendaring feature being used a lot and most of the fields in workeffort will be unused, so there will be a tremendous amount of wasted storage if I go that route.
What do you mean by wasted storage? Do you mean for the empty columns and such?
In general this isn't an issue for databases. The physical storage they use generally just leaves out nulled columns. In other words, it's not like they use a huge fixed width flat file for storing things or something, so the impact of extra columns that are used in your scenario is generally minimal, often hardly noticeable.
The real point of the OFBiz data model is to fit the needs to many different requirements. The best way to go, even if there is functionality you don't need, is to base it on what exists and simplify your custom UI as needed. And who knows, maybe in the future the extra structure and functionality might save your bacon.
-David
smime.p7s
Description: S/MIME cryptographic signature
