🚀 go-pugleaf

Bowen Moursund wrote:

> Design flaw!!

It cuts both ways. You may not want the master-detail constrain applied 
for every row, just to have to canGetRow throw out that record. If your 
canGetRow condition had nothing to do with the detail, and the hit rate 
was, say, 1 in 5, that would be a waste. OTOH, it might be more likely 
that if you're using canGetRow, it's for a condition that does rely on 
the master-detail.

> Zak, just *look* at all the code we wrote to do what the traditional DML
> can do with a single statement. It's heartbreaking! :-)

You must have confused me with Alan (somehow <g>) -- I've always said DML 
has its place. But with the increased granularity (which is mostly good), 
it's not as easy to write one-liners, unless you had a bajillion 
"behavior" properties -- aka SETs in another guise.

-- 
//Ken@Inprise
<Please follow-up to newsgroup; do not reply to email>