Hi Miguel,
You do have all the fun. Must be nice in Alentejo this time of year...
On Aug 13, 2007, at 3:42 PM, Miguel Arroz wrote:
Hi!
Have you tried
a.removeObjectFromBothSidesOfRelationship( obj, bs );
Same result.
I thought so, but it was worth a try.
Have you made other
Hi!
On 2007/08/14, at 17:03, Chuck Hill wrote:
Hi Miguel,
You do have all the fun. Must be nice in Alentejo this time of
year...
Friday. Friday I go there. Right before the border with Spain,
Serpa is where I'll go. Good food. Sun. Pool. The bad news is... I
come back Sunday.
I
On Aug 14, 2007, at 9:25 AM, Miguel Arroz wrote:
Hi!
On 2007/08/14, at 17:03, Chuck Hill wrote:
Hi Miguel,
You do have all the fun. Must be nice in Alentejo this time of
year...
Friday. Friday I go there. Right before the border with Spain,
Serpa is where I'll go. Good food. Sun.
Hi!
On 2007/08/14, at 17:40, Chuck Hill wrote:
See, it is trying to create an UPDATE statement for this object.
Something has trashed the EC state.
Maybe try adding
ec.undoManager().removeAllActions(); before the call to saveChanges
(), or try getting rid of the undo manager before making
On Aug 12, 2007, at 3:52 PM, Miguel Arroz wrote:
Hi!
This one should be simple.
I have object A that has a to-many relationship to B. So, A
contains Bs.
I fetch A that contains one B. Then, I add another B to the
relationship. Some other app deletes the B that was there before,
Hi!
On 2007/08/13, at 17:24, Chuck Hill wrote:
How do you handle this kind of problem?
By not disabling merging of changes. :-)
(I don't know if it's relevant, but the merging of changes is
disabled for the context).
I guess that it is relevant, though I don't recall doing this.
On Aug 13, 2007, at 1:10 PM, Miguel Arroz wrote:
Hi!
On 2007/08/13, at 17:24, Chuck Hill wrote:
How do you handle this kind of problem?
By not disabling merging of changes. :-)
(I don't know if it's relevant, but the merging of changes is
disabled for the context).
I guess that
Hi!
On 2007/08/13, at 21:35, Chuck Hill wrote:
I'm going to test this. But why is it relevant, if the deletion
of the first object happens in a different app? What exactly is
being merged here?
If it is in another app or another OSC then you won't get the error
that you mentioned.
On Aug 13, 2007, at 1:42 PM, Miguel Arroz wrote:
Hi!
On 2007/08/13, at 21:35, Chuck Hill wrote:
I'm going to test this. But why is it relevant, if the deletion
of the first object happens in a different app? What exactly is
being merged here?
If it is in another app or another OSC
Hi!
On 2007/08/13, at 21:44, Chuck Hill wrote:
Then something in your app is refreshing the to-many relationship.
Well, the problem is much more strange than I thought (we are
entering the you surely know how to have fun with WO zone!).
I have the a.bs() to-many relationship.
I
On Aug 13, 2007, at 2:56 PM, Miguel Arroz wrote:
Hi!
On 2007/08/13, at 21:44, Chuck Hill wrote:
Then something in your app is refreshing the to-many relationship.
Well, the problem is much more strange than I thought (we are
entering the you surely know how to have fun with WO zone!).
Hi!
Have you tried
a.removeObjectFromBothSidesOfRelationship( obj, bs );
Same result.
Have you made other changes in the EC? If not, ec.revert() should
handle all this much more cleanly.
I did! :( The problem is this: the user changes one object. Then,
I'm going to try to save the
Hi!
This one should be simple.
I have object A that has a to-many relationship to B. So, A
contains Bs.
I fetch A that contains one B. Then, I add another B to the
relationship. Some other app deletes the B that was there before, and
saves changes. When I save changes on my app, I
Hi!
Ok, here goes another one.
I need to change some objects in a context, and saveChanges.
saveChanges may, or may not fail, depending on OL failures. Nothing
new so far.
The problem is that I need to delete a lot of objects, possibility
thousands or tens of thousands. As I can't
You might be able to do it by overriding
databaseContextWillPerformAdaptorOperations on a database context
delegate and inject your own adaptor operations? I've never tried
this but I think that will let you do what you want ...
ms
On Aug 8, 2007, at 1:51 PM, Miguel Arroz wrote:
Hi!
EXTEND ERXDatabaseContextDelegate ... don't replace it. Or use
Chuck's multidelegate thing.
On Aug 8, 2007, at 1:51 PM, Miguel Arroz wrote:
Hi!
Ok, here goes another one.
I need to change some objects in a context, and saveChanges.
saveChanges may, or may not fail, depending on OL
My reply was too big with the attachments, so I moved my response
into the wiki:
http://wiki.objectstyle.org/confluence/display/WO/
Programming__WebObjects-EOF-Using+EOF-Problems
The last one, Strange Locking Problems ... And for the lazy:
It would appear that there is, in our opinion, some
This is pretty amazing Mike.
I'm having this exact problem right now, and have been banging my
head against the wall, saying THIS IS NOT POSSIBLE!. Apparently...
it is.
Now that the problem is identified, is there a reasonable solution?
Ken
On Aug 2, 2007, at 7:58 AM, Mike Schrag wrote:
hi mike
what you are describing here relieves my heart! back in february
(https://sourceforge.net/mailarchive/message.php?msg_id=ce7f98ec0702010654w560f4a8dxd6420d6dc39580f3%40mail.gmail.com)
i tried to argue why i needed a seperate osc because i was having the
blow-away-other-changes-in-the-EO
Unfortunately, there really isn't an obvious fix for this right
now ... I was going to try to dig in to EODBC this weekend and see if
it is a tweakable, but it's pretty well down in there, and even if
it is tweakable, it's a really complicated problem that could be made
a lot worse by a
I've never used it, but it's also MAYBE possible that turning on the
pessimistic locking strategy might be a fix, too? The potential
downfalls of that are huge, though.
ms
On Aug 2, 2007, at 8:41 AM, Ken Anderson wrote:
This is pretty amazing Mike.
I'm having this exact problem right
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
pple.com]O
n Behalf Of Oliver Egger
Sent: Thursday, August 02, 2007 2:36 PM
To: Mike Schrag; Development WebObjects
Subject: Re: Concurrency question
hi mike
what you are describing here relieves my heart! back
On Aug 2, 2007, at 6:57 AM, Mike Schrag wrote:
Unfortunately, there really isn't an obvious fix for this right
now ... I was going to try to dig in to EODBC this weekend and see
if it is a tweakable, but it's pretty well down in there, and
even if it is tweakable, it's a really
Of Oliver Egger
Sent: Thursday, August 02, 2007 2:36 PM
To: Mike Schrag; Development WebObjects
Subject: Re: Concurrency question
hi mike
what you are describing here relieves my heart! back in february
(https://sourceforge.net/mailarchive/message.php?msg_id=ce7f98
oops. Thank you for the clarification.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
pple.com]O
n Behalf Of Chuck Hill
Sent: Thursday, August 02, 2007 6:39 PM
To: Ruenagel, Frank
Cc: Webobjects-dev@lists.apple.com
Subject: Re: Concurrency question
Hi!
Well, I think the best solution would go the way as Core Data
went. Basically, the lucky guys I know who do all the bells and
whistles with desktop apps say that Core Data editing contexts are
independent. IE, no auto-updating, no problems at all.
I don't know if going no
Hi!
The contexts are locked. The problem is that it's not the same
context - it's a different context per thread, with local copies of
the same objects.
Synchronizing solves the sample problem, but as my real problem is
much more complex than this example, it starts to get a
Hi!
On 2007/08/01, at 18:14, Chuck Hill wrote:
You sure do know how to have fun with WO!
My software development cycle is a really weird thing. I'm a very
pessimistic guy, and I always assume everything will screw up. So I
start to think on all the ramifications I can get. When
Turn it off! See attached!
Miguel Arroz wrote:
btw, apple, you *could* do that popping up a little less stressful!
inline: pastedGraphic.tiff ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list
You can simulate OL, by listening to merge notifications. If it
affects a modified object you can later on refuse to save.
Pierre
On Aug 1, 2007, at 7:18 PM, Chuck Hill wrote:
On Aug 1, 2007, at 5:00 AM, Miguel Arroz wrote:
Hi!
The contexts are locked. The problem is that it's not
The problem comes in when the modifications are made and saved after
your editing context has been locked in the RR loop. I tricked ;-)
Mike into looking at this today with. Looks like tigers lurk here.
Maybe Mike will comment.
Chuck
On Aug 1, 2007, at 2:34 PM, Pierre Bernard wrote:
Hi!
I'm trying to understand what's the best way to do something here.
Imagine that I need to get a object from the database, modify some
attribute based on itself and save it again.
So, we have the method:
public void incrementIt() {
if( aIsEven() ) { // 1
Miguel,
Is your editing context locked before calling incrementIt() ? I
would think that would solve your concurrency issue here.
If not, just synchronizing the method should solve the problem. It
may seem inelegant, but you really ARE solving 2 different problems...
Ken
On Jul 31,
33 matches
Mail list logo
