Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Yes you are going against best practices. In that use case, if you really do not want to save the objects, keep them in an intermediate format and only create a Core Data object for the one you want to persist. However this seems quite wrong.</p> <p>What is the harm in saving the other books? Are the only going to be used once ever?</p> <p>Based on the small amount of information you have provided, it seems your approach to the problem needs to be reconsidered.</p> <h2>Update</h2> <p>Removing unsaved objects from the context has a very small overhead yes so that is the best solution given the parameters you have. I asked the other questions to see if there was a cleaner overall solution rather than building the objects just to throw them away. Sounds like you have already been down that path though.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to not persist NSManagedObjects retrieved from NSManagedObjectContext
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMarcus S. Zarra
    1. USMarcus S. Zarra
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to not persist NSManagedObjects retrieved from NSManagedObjectContext
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHi Marcus and thanks. I can see there is not much info to work with. My main grievance with building intermediate objects is that I will have to build X implementations. There are use cases where I automatically add some books to the persistent store, where many books will be added and situations like above where only one should be persisted. I will also have to maintain Book and tempBook and populate the values from one to the other "manually", as far as I know, there is no "copy values from NSObject to NSManagedObject". Core Data is surely fast enough that it would keep things very 'clean'.
      singulars
      1. PO
      1. USRickiG
    2. COran out of characters. Yes books are mostly only used that one time. I also have "collections of books" entities(not containing actual books, just enough info to retrieve a set of books) that follows the above use cases, I have author entities and publisher entities that behaves in very similar manners. Using Core Data and NSPredicate I can keep things very transparent, with an overhead that is almost non existing.
      singulars
      1. PO
      1. USRickiG
    3. COI found this one:http://stackoverflow.com/questions/1619911/how-do-i-create-many-temporary-objects-and-then-save-only-one-using-core-data I went through the documentation again and it states that sending the deleteObject:Book message to a book that is not yet saved, has very little overhead as it simply removes the book from the context, no interaction with the store is needed.
      singulars
      1. PO
      1. USRickiG
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload