Uniquing an Object #9

New Issue

2025-12-29T18:21:21+01:00

adam commented

2025-12-29 18:21:21 +01:00

Originally created by @PaulWoodIII on GitHub (Jul 31, 2015).

I've got a recommendation for some additional documentation, and by the way your documentation is great, Its obvious that you care so thats why I'm recommending some more

How to fetch or create a unique object, below is my current way of doing it but I'd like to know your way and I think others would like to know as well

CoreStore.beginAsynchronous { (transaction) -> Void in
    let uniqueIDValue = "a unique id string"
    var madeEvent = transaction.fetchOne(From(Event), Where("uid == %@",uniqueIDValue))
    if madeEvent == nil {
        madeEvent = transaction.create(Into(Event))
    }
    guard let eventObj = madeEvent else {
        return
    }
    eventObj.uid = uniqueIDValue
    //Set any other attributes
    transaction.commit()
}

Originally created by @PaulWoodIII on GitHub (Jul 31, 2015). I've got a recommendation for some additional documentation, and by the way your documentation is great, Its obvious that you care so thats why I'm recommending some more How to fetch or create a unique object, below is my current way of doing it but I'd like to know your way and I think others would like to know as well ``` swift CoreStore.beginAsynchronous { (transaction) -> Void in let uniqueIDValue = "a unique id string" var madeEvent = transaction.fetchOne(From(Event), Where("uid == %@",uniqueIDValue)) if madeEvent == nil { madeEvent = transaction.create(Into(Event)) } guard let eventObj = madeEvent else { return } eventObj.uid = uniqueIDValue //Set any other attributes transaction.commit() } ```

adam added the discussion label 2025-12-29 18:21:21 +01:00

adam closed this issue

2025-12-29 18:21:21 +01:00

adam commented

2025-12-29 18:21:21 +01:00

@JohnEstropia commented on GitHub (Jul 31, 2015):

@PaulWoodIII
Personally I'll just write it like this

CoreStore.beginAsynchronous { (transaction) -> Void in
    let uniqueIDValue = "a unique id string"
    let event = transaction.fetchOne(From(Event), Where("uid == %@",uniqueIDValue))
        ?? transaction.create(Into(Event))
    event.uid = uniqueIDValue
    //Set any other attributes
    transaction.commit()
}

But that's totally just aesthetic preference and depends entirely on other requirements. You should be free to decide your own best practice.

Your comment's timing is really good though. The next in CoreStore's roadmap is Data importing utilities for transactions. While the fetch-or-create pattern is common, part of the optimization utilities I'm designing is for uniquing multiple objects when importing from an external source. In pseudo-code,

get all IDs from the external source
fetch all existing objects in one fetch request using the array of IDs
update each fetched object
create the rest of the non-existent IDs
update each created object

Instead of doing 1 fetch/create each loop, this saves a lot of I/O by doing all fetches in one request and just loop creation on the non-existent items.

@JohnEstropia commented on GitHub (Jul 31, 2015): @PaulWoodIII Personally I'll just write it like this ``` swift CoreStore.beginAsynchronous { (transaction) -> Void in let uniqueIDValue = "a unique id string" let event = transaction.fetchOne(From(Event), Where("uid == %@",uniqueIDValue)) ?? transaction.create(Into(Event)) event.uid = uniqueIDValue //Set any other attributes transaction.commit() } ``` But that's totally just aesthetic preference and depends entirely on other requirements. You should be free to decide your own best practice. Your comment's timing is really good though. The next in CoreStore's roadmap is _Data importing utilities for transactions_. While the fetch-or-create pattern is common, part of the optimization utilities I'm designing is for uniquing multiple objects when importing from an external source. In pseudo-code, - get all IDs from the external source - fetch all existing objects in one fetch request using the array of IDs - update each fetched object - create the rest of the non-existent IDs - update each created object Instead of doing 1 fetch/create each loop, this saves a lot of I/O by doing all fetches in one request and just loop creation on the non-existent items.

adam referenced this issue

2025-12-29 18:22:00 +01:00

Exposing NSManagedObjectContext #54

Sign in to join this conversation.

Branches Tags

develop

prototype/swift6

master

prototype/concurrency

minIOS13

prototype/containers

transactionSourceTracking

prototype/swiftui

minIOS11

swift5_3

prototype/propertyWrapperFields

prototype/propertyWrappers

prototype/propertyWrapper

Swift5

throwables

prototype/Swift_4_1

prototype/Swift_4_0

prototype/Swift_3_2

prototype/queryBuilders

temp/develop

corestore4_develop

prototype/mainContextToPSC

master_ios_7_to_9

swift_2_3

gh-pages

_corespotlight-test

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/CoreStore-JohnEstropia#9