Databases
StackOverflow2013
Postsdbo
POSplit Data for NSKeyedArchiver and NSKeyedUnarchiver
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSplit Data for NSKeyedArchiver and NSKeyedUnarchiver
    primarykey
    data
    text
    <p>Edit (2012/10/22): Restating this question in hopefully clearer terms.</p> <p>Essentially, what I'm looking for is some NSCoder that can (un)archive between multiple locations. Some of the encoded objects primitives should be saved in location A while others should be saved in specified location B, etc.</p> <p>For example, suppose we have a class with something like this:</p> <pre><code>@interface SomeClass { NSString *ivar1; NSString *ivar2; NSString *ivar3; SomeClass *ivarZ; } ... @end </code></pre> <p>Somewhere we have an instance:</p> <pre><code>SomeClass *someObject; </code></pre> <p>What I want to do is something like the following on saving:</p> <pre><code>NSData *prefDat = [KeyedMultiArchiver archiveRootObject:someObject withPartitionKey:@"DataForNSUserDefaults"]; NSData *permDat = [KeyedMultiArchiver archiveRootObject:someObject withPartitionKey:@"DataForPermanentStorage"]; /* save prefDat to NSUserDefaults */; /* save permDat to some appropriate NSURL */; </code></pre> <p>And then on unarchiving:</p> <pre><code>SomeClass *anotherObject = [SomeClass new]; NSData *prefDat = /* get from NSUserDefaults */; NSData *permDat = /* get from appropriate NSURL */; [KeyedMultiUnarchiver unarchiveData:prefDat intoObject:anotherObject withPartitionKey:@"DataForNSUserDefaults"]; [KeyedMultiUnarchiver unarchiveData:permDat intoObject:anotherObject withPartitionKey:@"DataForPermanentStorage"]; </code></pre> <p>Where <code>ivar1</code>s might get saved to <code>NSUserDefaults</code> and <code>ivar2</code>s, <code>ivar3</code>s to disk somewhere.</p> <p>I'll probably end up coding my own solution for this, but if you guys come up with any brilliant alternatives please let me know!</p> <p>Will post final product.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USKara
    1. USNcat
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COI think you need to provide a little more detail about your structure. Is it a top level dict with mutable data and immutable data below it, or is the mutable data scattered around your immutable data structure?
      singulars
      1. POSplit Data for NSKeyedArchiver and NSKeyedUnarchiver
      1. USGordon Dove
    2. COIt's at least 3 levels deep. Each object in each layer may have one of or both immutable and mutable data. From the global point of view, there is no systematic split between mutable and immutable properties; each class in the hierarchy decides for itself. I'm hoping to have the data serialization logic centralized as much as possible--would prefer to keep individual classes saving and loading their individual data or anything of that sort.
      singulars
      1. POSplit Data for NSKeyedArchiver and NSKeyedUnarchiver
      1. USNcat
    3. COUnfortunately, just after posting this question, the project became temporarily stopped, so I haven't been able to fix it yet. However, one (desperate) solution I thought of was to rewrite the serialization code to use Core Data instead. I'm really hoping to avoid this, so any suggestions are much appreciated.
      singulars
      1. POSplit Data for NSKeyedArchiver and NSKeyedUnarchiver
      1. USNcat
 

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