On Apr 24, 2006, at 6:54 PM, Louis Demers wrote:
At 6:36 PM -0400 2006/04/24, Paul Suh wrote:
Louis,
If I understand your problem correctly, you would like to put in an
audit trail whenever a user opens an EO for editing, and again once
the EO is actually changed, right?
Yes, I wanted to a
At 10:27 AM -0700 2006/04/24, Chuck Hill wrote:
Hi Louis,
I'd like to try an add some clarification to the issue(s) being
discussed. I think there are a couple of overlapping areas that
could benefit from some more examination.
... ( a very good overview)
What people are saying is that it
At 6:36 PM -0400 2006/04/24, Paul Suh wrote:
Louis,
If I understand your problem correctly, you would like to put in an
audit trail whenever a user opens an EO for editing, and again once
the EO is actually changed, right?
Yes, I wanted to avoid using the word audit simply because I'm not
n
Louis,
If I understand your problem correctly, you would like to put in an
audit trail whenever a user opens an EO for editing, and again once
the EO is actually changed, right? In that case, you can trigger a
save to the object graph before the user ever sees the page. The
sequence of ac
Hi Louis,
I'd like to try an add some clarification to the issue(s) being
discussed. I think there are a couple of overlapping areas that
could benefit from some more examination.
One of the central responsibilities of EOF is to ensure object graph
consistency. There are three views of
At 3:22 PM -0400 2006/04/21, Paul Suh wrote:
Louis,
Trying to save a single EO while leaving others unsaved is almost
always indicative of a problem in your application's design
That was my initial concern and the reason I asked the question on
how to do it, knowing I would be corrected
Ken,
On Apr 21, 2006, at 9:57 PM, Ken Anderson wrote:
Also, I highly suggest never, ever, using hackery in EOF to
partially save an EC... and I speak from experience :)
Well... in, how long it is this project runs? Four-odd years, and I
am yet to encounter the first runtime problem caused
On Apr 21, 2006, at 3:57 PM, Ken Anderson wrote:
Also, I highly suggest never, ever, using hackery in EOF to
partially save an EC... and I speak from experience :)
AMEN!!
--Paul
Paul Suh
http://www.ps-enable.com/
[EMAIL PROTECTED]
Ondra,
This is a situation that cries out for nested and peer editing
contexts. Each Volume should have its own peer EC. Each Page then has
an EC whose object store is the Volume's EC. Remember that different
EC's can each have their own copy of the same EO, each of which has
the same EOG
Ondra,
The general rule I go by, which fits EOF, is that if the user has a
save button on a window/panel whatever, it saves the entire object
graph. Obviously, there's no reason they can't have multiple
documents/windows open peering into different parts of your object
graph.
There's n
Paul,
On 21.4.2006, at 21:22, Paul Suh wrote:
You should probably go back and re-think your design, so that you
are no longer trying to save the single EO -- instead, your natural
flow will be to save the entire state of the object graph tracked
by the EC.
My archetypal wanna-save-part-o
On Apr 21, 2006, at 11:32 AM, [EMAIL PROTECTED]
wrote:
I would like to save newly created EO immediately but there could be
other objects in the default EditingContext which I do not want to
commit to the database immediately.
My first attempt was to create a new short term EditignContext,
in
) 643-1516
On Apr 21, 2006, at 11:32 AM, [EMAIL PROTECTED]
wrote:
Message: 3
Date: Fri, 21 Apr 2006 00:19:51 -0400
From: Louis Demers <[EMAIL PROTECTED]>
Subject: How to selectively save EO
To: WebObjects-List Apple
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; ch
Ondra,
I'm not sure what the problem is - it makes perfect sense, since an
editing context is a single perspective onto data. If you want to
save other objects prior, you can also have child editing contexts
that will commit changes to the parent.
Note that you can cross contexts with sh
Louis Demers wrote:
Hi
I would like to save newly created EO immediately but there could be
other objects in the default EditingContext which I do not want to
commit to the database immediately.
My first attempt was to create a new short term EditignContext, insert
my newly created EO in it
Ken,
On Apr 21, 2006, at 1:52 PM, Ken Anderson wrote:
A golden rule is that all related objects have to be in the same
editing context
I've bumped into this problem once or twice myself (and, Louis, alas,
have not found a good solution in EOF). Time to time it might be
reasonable to have
Louis,
First off, please start a new message instead of replying to an old
message and changing the subject. It messes up people organizing
their email by thread.
On Apr 21, 2006, at 12:19 AM, Louis Demers wrote:
Hi
I would like to save newly created EO immediately but there could
be
See comments below:
Louis Demers wrote:
Hi
I would like to save newly created EO immediately but there could be
other objects in the default EditingContext which I do not want to
commit to the database immediately.
My first attempt was to create a new short term EditignContext, insert
my n
Hi
I would like to save newly created EO immediately but there could be
other objects in the default EditingContext which I do not want to
commit to the database immediately.
My first attempt was to create a new short term EditignContext,
insert my newly created EO in it and call saveChanges
19 matches
Mail list logo
