Quote Originally Posted by PAVB
I'm really sorry Bob but this is all wrong.

Citldba was really nice to you when saying "there is no right or wrong answer" but the naked truth is that there is a right and wrong answer... and this is all wrong.
That is a harsh statement!


Quote Originally Posted by PAVB
1- As stated you want to build a "generic solution" ideally PHP/MySQL
I said I was looking for a "platform independent" solution, but that I would likely implement - for now - using PHP/MySQL.

What is wrong with that?


Quote Originally Posted by PAVB
2- Your notation looks like SQL Server standard
It is Microsoft nomenclature...

So?


Quote Originally Posted by PAVB
3- You are asking in an Oracle forum
Right. Because I think Oracle people are some of the smartest and closer, philosophically - to what I want to achieve. So?


Quote Originally Posted by PAVB
4- You are "modeling" -or did you mean "prototyping" - in MS-Access
Right, I started a prototype in MS Access, but I want a solution that meets enterprise database standards (e.g. Oracle). So?


Quote Originally Posted by PAVB
5- Your concepts of data modeling are all over the place -not necessarily good places.
How so?

Then what do YOU propose as a solution? (I listed 5 different scenarios.)


Quote Originally Posted by PAVB
I'll point just to one random issue here...

...let me break the news for you, in your scenario a "quantity" of something you are buying is a "quantity" no matter what you are buying.
Maybe, I know lots of people - Oracle included - who would disagree.

From a datatype standpoint alone, I disagree.

You don't buy 10.57 bananas!

"ItemQuantity" is an Integer. "TotalGallons" is a Real number. As such, they aren't logically the same thing. But regardless, that is the LEAST of my worries.

If you have a better "Data Modeling solution", then please share it here.

Thanks,


Just Bob