101 reputation
bio website
location United Kingdom
age
visits member for 2 years, 11 months
seen Jan 10 '12 at 22:59

Dec
14
comment two approaches to database modeling - which one to use when
EAV tables are not an Oracle specific concept. It's just a much more highly normalised way of representing the data - with many benefits and issues. As in the other comments, there is much on-line that discusses EAV. It's something that is initially very attractive to generalists, but it really does have its costs too.
Dec
14
comment two approaches to database modeling - which one to use when
Extendible numbers of properties is definitely one property. But it also removes the need for a NULL value - Simply don't have the value in the EAV table. There are many more properties (positive and negative) than a SO answer (or comment) could list, it really is something to check on the web rather than here.
Dec
13
comment Worst practices in developing database applications
I'm nt saying it is always okay, I'm just saying that the problem isn't nested SPs per-se, it's how the SPs have been logically broken down.
Dec
13
comment Worst practices in developing database applications
In what way is 18 nested SPs a bad practice? A program is a very deeply nested set of method calls. Is it not the case that the functional encapsulation matters most - that the problem does logically break into 18 re-usable pieces?