Hello All, I have an app that creates a large and complex graph structure. It's working nicely now, after a fairly lengthy development process, but I'm having scaling issues -- the data structure gets too big to keep in memory. So, I'm thinking about Core Data. The thing is, the process of building the object graph is very specific (it's a complex undirected graph structure, built via machine learning) and since I've got it working properly I really don't want to port the whole thing over to Core Data, since that would just be begging for a huge headache, I'm sure.
All of the data is held in NSMutableDictionaries (basically working as adjacency lists), owned by one particular class. What I'm wondering is whether there's some way to use Core Data to perform the work of the dictionaries, without necessarily rebuilding all of the object relationships etc. using Core Data entities? Looking around a bit it looks like "Transformable" attributes might offer a solution. What I'd like to do is to basically swap out the NSMutableDictionaries for Core Data entities that store my custom objects as transformable attributes. Is that at all feasible? Worth trying? Thanks in advance. J. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
