Re: OO and relation "impedance mismatch"
From: Kenneth Downs <firstinit.lastname_at_lastnameplusfam.net>
Date: Wed, 06 Oct 2004 14:10:09 -0400
Message-ID: <0ec1kc.83b.ln_at_mercury.downsfam.net>
> I will
> believe
> proven it
> more
>
> I look forward to it. As I have said before, I know for a fact that
> your approach wouldn't work 100% for Oracle (which doesn't even support
> dirty reads), but I can't be so sure about other DBMSs.
Date: Wed, 06 Oct 2004 14:10:09 -0400
Message-ID: <0ec1kc.83b.ln_at_mercury.downsfam.net>
Tony Andrews wrote:
>> To recap: >> >> My use of triggers is currently experimental. I know for a fact that
> I will
>> trade performance to get my preference for show-me-all-errors. I
> believe
>> *intuitively* that I can get 100% data protection, but I have not
> proven it
>> yet to my own satisfaction. Stay tuned, you will undoubtedly hear
> more
>> from me as I work on the project.
>
> I look forward to it. As I have said before, I know for a fact that
> your approach wouldn't work 100% for Oracle (which doesn't even support
> dirty reads), but I can't be so sure about other DBMSs.
I have not used Oracle yet seriously, but considering most colleagues who have tell me it can "everything", I would be willing to be a dollar that it can somehow do it by another name. For instance, DB/2 calls it a "non-repeatable read", which name is self-explanatory, though perhaps it should have been called "potentially non-repeatable read."
-- Kenneth Downs Use first initial plus last name at last name plus literal "fam.net" to email meReceived on Wed Oct 06 2004 - 20:10:09 CEST