• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Ghost row in EOF
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Ghost row in EOF


  • Subject: Ghost row in EOF
  • From: Gino Pacitti <email@hidden>
  • Date: Wed, 3 Dec 2003 14:33:43 +0000

From: Gino Pacitti <email@hidden>
Date: Wed Dec 3, 2003  1:01:32  pm Europe/London
To: email@hidden
Cc: email@hidden
Subject: Ghost row in EOF

Hi,

I thought I knew enough about  the EOF stack but I was mystified by
this behaviour.

I have an app that was running in deployment and it has an web based
administration area where records can be added, modified, deleted etc..

And the actual website where the records can be viewed, a shopping cart.

I understood from the docs that by default EOF used a single stack and
shared the control layer and access layer across sessions.
Each user having there own session defaultEditingContext.

By this I understood that each user has there own object graph based
upon the fetch that was initiated from their context ( the page that
they were on and the records required).

What occured was that I had two open sessions

session 1  for admin deleting a record
session 2  user at main with a set of records loaded and faults not
fired for related items

When the admin removed the object using saveChanges() all seems well.

<!-- start code snippet -->


items.removeObject(itemSelected);
EOEditingContext eContext = itemSelected.editingContext();
             eContext.deleteObject(itemSelected);
             eContext.saveChanges();
<!-- end code snippet -->

But when the user actually went to views the records in session 2 the
browers showed an empty row in the displaygroup iteration - it seemed
like a ghost object?

Do sessions have access to a shared snapshot in the EOF stack or share
cached fetches that were initiated by other users or is there
notification across sessions ?

BTW when I used  eContext.refreshAllObjects() after the saveChanges();
the condition rectified and the ghost row was not visible?

Could anyone perhaps explain this phenomenon or correct my
mis-comprehension of EOF stack.

Best

Gino
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.

  • Prev by Date: Re: Postgresql Adaptor?
  • Next by Date: Re: Postgresql Adaptor?
  • Previous by thread: Re: Postgresql Adaptor?
  • Next by thread: Re: Ghost row in EOF
  • Index(es):
    • Date
    • Thread