Re: EOF inserts PK automatically
Re: EOF inserts PK automatically
- Subject: Re: EOF inserts PK automatically
- From: "Ruenagel, Frank" <email@hidden>
- Date: Mon, 22 Nov 2004 11:55:15 +0100
Of course it is not the standard. And of course "starters" should
not do this. You are right. If you use this, you'll have to think
carefully about the consequences. It does not work in all contexts.
In mine it does. The concurrency problem can be avoided. Simply
use an identifier.
Transaction Problem:
There is no insert outside the stored procedure. So why should
there rise a problem?
You can't use triggers or reasonable contraints: yes, you are right.
To be clear: not recommended. Of course. But sometimes we are forced
to solve problems and to do things which are not standard.
> -----Original Message-----
> From: Anjo Krank [mailto:email@hidden]
> Sent: Monday, November 22, 2004 10:59 AM
> To: Ruenagel, Frank
> Cc: 'email@hidden'; 'Chuck Hill'
> Subject: Re: EOF inserts PK automatically
>
>
>
> Am 22.11.2004 um 10:00 schrieb Ruenagel, Frank:
>
> > Dear Chuck, are there any reasons why this should not work?
>
> For starters, you can't use DB triggers or reasonable constraints on
> your fake record, you are (AFAIK) acting outside of the transaction
> that does the actual insert, your concurrent searches might find this
> dummy record and if I'd actually put my mind into, I'd probably find
> half a dozen more reasons why you shouldn't do this...
>
> Cheers, Anjo
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden