Hi again,

Graph does a great job handling everything I need, except, I'm a closed minded developer who needs every object to be immaculate. Anyways, Referring every object I'm working with as Entity and pass them around is something I can't get my head around it. Maybe I'm seeing it from a wrong perspective (it's highly likely), but I cannot find a good resource on it.

I tried to overcome this dilemma by introducing custom types based on Entity and simply add properties based on my needs to the Entity based objects. Here is an example:

class MyObject: Entity {

  private struct FieldNames {
  static let EntityType = "MyObject"
    struct Properties {
      static let Field1Name = "field1"
      static let Field2Name = "field2"
    }
  }

  var Field1: String? {
    return self[FieldNames.Properties.Field1Name] as? String
  }

  var Field2: String? {
    return self[FieldNames.Properties.Field2Name] as? String
  }
}

This way I can work with entities in a more civilized manner. I have actually a more complex set of properties and they synchronize with graph with ease but I don't want to get into that for now.

Now the problem: Because Graph returns Entity objects and they are initialized as Entity I can't downcast them to my own types. It seems obvious, I know. Extending Entity is not an option here because it affects all Entityobjects not just my types.

Needless to say, all these goes for Relationships too.

Questions: 1- Is this a good pattern at all? Am I wrong thinking about such solutions and should swallow the pill and work with graphs as they are intended to work? I'm still thinking in pure CoreData mindset which I had control over my object types. (Pattern - AntiPattern)

2- How can I overcome this dilemma? I was under the impression that I can make custom type converters but apparently I was wrong. How do you think I can make this work?

3- Is it a good idea to design the object as a composite (I'm not even sure I'm using the right pattern name here) and use the entity as an internal mechanism to return values based on that? Something like this:

class MyObject {
  private struct FieldNames {
  static let EntityType = "MyObject"
    struct Properties {
      static let Field1Name = "field1"
      static let Field2Name = "field2"
    }
  }
  let entity: Entity!
  init?(entity: Entity){    
    self.entity = entity
    guard entity.type == FieldNames.EntityType else {
      return nil
    }
  }

  var Field1: String? {
    return entity[FieldNames.Properties.Field1Name] as? String
  }

  var Field2: String? {
    return entity[FieldNames.Properties.Field2Name] as? String
  }

}

Is there any caveat in doing so? Memory leaks maybe? Synchronization?

Just make a new project, turn on iCloud, make an instance of Graph using the cloud init (where is not clear the purpose of the string you have to pass), make a new record and save the db, and finally setup a search, run it and you'll see the returned array is always empty

Would love to see some wikipedia links to these subjects:

Relationship Modeling Action Modeling For Analytics Model With Graph Theory and Set Theory Faceted Search API

Or other good links/books

Hi, first off, I would like to say that I love the concept. I've been using it for a few days and I would like to ask if there is an optimized way that you'd recommend for searching for a specific entity with a specific property. I've been time profiling the app I'm using and for comparing 350 entities that already exist in the Graph, its taking roughly 10 seconds.

How can we delete the relationship and their all relationships(subject and object). Seems like when trying to relationship.delete() will not delete its Entities(subject and object).

Hi, is there any plans for providing a way to pass the graph location when creating ? Imagine that I want to share data between an iOS app and a Today Extension, I would have to use a shared container, which means Graph would have to be located there.

How could i do that using Graph ?

Hi all, especially Daniel :)

I'm in a need including Entity vars in a struct that conforms to Codable (as of Swift 4).

Not sure if that makes sense in regards to the Graph API philosophy, but to me, that'd be useful as I wouldn't need to remodel the Entity's structure.

Thanks for Graph anyway - what a decent piece of great software!

Best wishes,

Karsten

i would like to implement the cloud feature of graph. I ve searched on cosmicmind site, here on the repo (looking for wiki), and through the issues (closed). I have just learnt that feature is available, but i did not find any documentation.

Considering i am already using graph, in local:

let graph = Graph()
let entityPfx = "entityPfx"
let search = Search<Entity>(graph: graph).for(types: entityPfx)
let results = search.sync()

I would like users could retrieve data from the cloud in case of device upgrade or so. Is there any documentation available in order to implement this? Thank you.

Referring to https://stackoverflow.com/questions/48667199/migrate-database-from-local-to-cloud-with-graph

Hi guys, while testing your library I've made an app and installed crashlytics so I could track errors. I've come across this stack trace a couple of times now :

Thread : Crashed: com.jarm.testGraph.dataBaseQueue 0 libobjc.A.dylib 0x19938dbd0 objc_msgSend + 16 1 CoreData 0x18444210c -[NSManagedObjectContext(_NSInternalAdditions) _retainedObjectWithID:optionalHandler:withInlineStorage:] + 84 2 CoreData 0x184482f80 -[_NSFaultingMutableSet willReadWithContents:] + 576 3 CoreData 0x184464f1c -[_NSFaultingMutableSet countByEnumeratingWithState:objects:count:] + 44 4 libswiftFoundation.dylib 0x101725848 TFC10Foundation15NSFastGenerator4nextfS0_FT_GSqPSs9AnyObject_ + 80 5 Graph 0x1005f1fa4 specialized ManagedEntity.subscript.getter (ManagedEntity.swift:64) 6 Graph 0x1005f0900 ManagedEntity.subscript.getter (ManagedEntity.swift:63) 7 Graph 0x1005c40c8 Entity.subscript.getter (Entity.swift:87) 8 testGraph 0x100089bd4 PersistanceManager.(createEntryFrom in _31C0B1288B530182F4EB108E0D3B2867)(Entity) -> Entry (PersistanceManager.swift:243)

I'm using a background thread to get the entity from Graph. So my question is: Is there a recommended way to fetch result from Graph in background threads ? Could it be done concurrently or only serially ?

Thanks for the help.

PS: IMHO this library would benefit from a detailed documentation, I don't know if that is on your backlog ;) I'd be happy to contribute to that if you like

private func internalSelect(x: RedBlackNode<Key, Value>, order: Int) -> RedBlackNode<Key, Value> {
    validateOrder(order)
    var r: Int = x.left.order + 1
    if order == r {
        return x
    } else if order < r {
        return internalSelect(x.left, order: order)
    }
    return internalSelect(x.right, order: order - r)
}

I keep getting " fatal error: unexpectedly found nil while unwrapping an Optional value (lldb) "

Seems to happen after hitting this line of code in my project var randomWordFromWords = graph.search(Entity: "Word")[randomNumber()]

I've set SWIFT_VERSION to 4.2 for the Graph pod but when compiling my workspace I get the following error in ManagedNode.swift line 55: Incorrect argument label in call (have 'stringInterpolationSegment:', expected '_cocoaString:')

The code in question is below. Apple documentation indicates that String(stringInterpolationSegment: should not be called directly. I tried amending the parameter as the error suggested but that just caused a runtime crash. I'm not clear what this code is trying to achieve exactly so can't recommend how to fix it. There's obviously something subtle going on as otherwise why not just use "(self.nodeClass)" instead? ( I tried changing the code to that too but caused runtime crash too).

        guard let moc = managedObjectContext else {
            fatalError("[Graph Error: Cannot obtain permanent objectID]")
        }
        
        var result: String?
        moc.performAndWait { [unowned self, unowned moc] in
            do {
                try moc.obtainPermanentIDs(for: [self])
            } catch let e as NSError {
                fatalError("[Graph Error: Cannot obtain permanent objectID - \(e.localizedDescription)]")
            }
            result = String(stringInterpolationSegment: self.nodeClass) + self.type + self.objectID.uriRepresentation().lastPathComponent
        }
        return result!
    }

Hi,

I found this library by chance, and it seems that it may be pretty helpful. I'm just starting, but I noticed that there are several deprecations:

• NSPersistentStoreUbiquitousTransitionType
• NSPersistentStoreUbiquitousContentNameKey
• NSPersistentStoreDidImportUbiquitousContentChanges
• NSPersistentStoreUbiquitousTransitionTypeKey

Xcode just tells "was deprecated in iOS 10.0: Please see the release notes and Core Data documentation." However, I did some googling and did not find anything that would give me an indication about how to replace those keys.

So, I'd like to report this to you, assuming that you know better by far than me what this might mean, and how to handle it...

• Hardy

Hi 👋

I'm facing a weird issue, when I run this code:

// initial.id is a UUID

let search = Search<Entity>(graph: Globals.graph).where(
    .type("Customers", using: &&)
        && "id" == initial.id as CVarArg // <- Is it the good way?
)

This causes a crash (here is the crashlog: https://pastebin.com/uk6em3p1).

But if I run this code, it works:

let search = Search<Entity>(graph: Globals.graph).where(.type("Customers"))
let entity = search.sync().filter {
    $0["id"] as! UUID == initial.id
}

Am I doing something wrong with the new API or is it a library issue? Thanks!

Hi, im using the latest stable version on graph im my project (i also tried development branch but the issue is there too). Since i updated to iOS 13, i am experiencing what looks like a bad error, which i will post here:

[error] fault: One or more models in this application are using transformable properties with transformer names that are either unset, or set to NSKeyedUnarchiveFromDataTransformerName. Please switch to using "NSSecureUnarchiveFromData" or a subclass of NSSecureUnarchiveFromDataTransformer instead. At some point, Core Data will default to using "NSSecureUnarchiveFromData" when nil is specified, and transformable properties containing classes that do not support NSSecureCoding will become unreadable.

CoreData: fault: One or more models in this application are using transformable properties with transformer names that are either unset, or set to NSKeyedUnarchiveFromDataTransformerName. Please switch to using "NSSecureUnarchiveFromData" or a subclass of NSSecureUnarchiveFromDataTransformer instead. At some point, Core Data will default to using "NSSecureUnarchiveFromData" when nil is specified, and transformable properties containing classes that do not support NSSecureCoding will become unreadable.

2020-01-03 18:39:45.842073+0100 APPNAME[50600:5957542] [error] CoreData: One or more models in this application are using transformable properties with transformer names that are either unset, or set to NSKeyedUnarchiveFromDataTransformerName. Please switch to using "NSSecureUnarchiveFromData" or a subclass of NSSecureUnarchiveFromDataTransformer instead. At some point, Core Data will default to using "NSSecureUnarchiveFromData" when nil is specified, and transformable properties containing classes that do not support NSSecureCoding will become unreadable.

Now some specific error: these errors are related to specific graph classes.

CoreData: warning: Property 'object' on Entity 'ManagedRelationshipProperty' is using nil or an insecure NSValueTransformer. Please switch to using "NSSecureUnarchiveFromData" or a subclass of NSSecureUnarchiveFromDataTransformer instead.

CoreData: warning: Property 'object' on Entity 'ManagedEntityProperty' is using nil or an insecure NSValueTransformer. Please switch to using "NSSecureUnarchiveFromData" or a subclass of NSSecureUnarchiveFromDataTransformer instead.

CoreData: warning: Property 'object' on Entity 'ManagedActionProperty' is using nil or an insecure NSValueTransformer. Please switch to using "NSSecureUnarchiveFromData" or a subclass of NSSecureUnarchiveFromDataTransformer instead.

I have no idea on how to solve this, and where to start, but it looked like a "Hey, you need to fix me asap or i can break your app and make it unasable". Hope you can address this in the development branch you currently are, waiting for a response from you and keep up the good work, graph is awesome.

func cancella(at offset: IndexSet) {
        guard let intindex = Array(offset).first else { return }
        let id = dm.Storage[intindex].properties["id"] as? String ?? ""
        DataManager.Shared.cancellaPosto(id)
    }

func cancellaPosto(_ ID: String) {
        let operazioneSearch = Search<Entity>(graph: DB).where(.type("Posti") && "id" == ID)
        let operazione =  operazioneSearch.sync(completion: nil)
        
        if let opeDaCanc = operazione.first {
            opeDaCanc.delete()
            if let index = Storage.firstIndex(of: opeDaCanc) {
                self.Storage.remove(at: index)
                self.objectWillChange.send()
            }
        }

        DB.async {(Bool, error) in
            if let e = error {
                print(e.localizedDescription)
            }
        }
    }

Fatal error: [Graph Error: Cannot obtain permanent objectID]: file /Users/schulz/Desktop/POI MapNote/POI MapNote/Graph/ManagedNode.swift, line 40 2019-12-09 15:53:14.847221+0100 Simple List[48128:2685330] Fatal error: [Graph Error: Cannot obtain permanent objectID]: file /Users/schulz/Desktop/POI MapNote/POI MapNote/Graph/ManagedNode.swift, line 40

Hi all,

when switching a project to Swift 5, I upgraded to Graph 3.1.1 (from 2.2.2 and now I get complaints like):

"Value of type 'Search' has no member 'for'"

As the Graph examples and documentation still use examples with 'for', I suggest upgrading the documentation to the new API.