groupingBlock never called with setPrimitiveData:

[chaitanyapandit]

Due to some optimizations, in my code am storing objects by archiving them myself and then calling setPrimitiveData: forKey: withPrimitiveMetadata: instead of setObject:...

This leads to one problem when I use views, where none of the the groupingBlock get called (Unless I change the version)

I understand that you need an 'object' to call the YapCollectionsDatabaseViewGroupingWithObjectBlock, but when using setPrimitiveData: grouping blocks of type
YapCollectionsDatabaseViewGroupingWithKeyBlock and YapCollectionsDatabaseViewGroupingWithMetadataBlock should be called.

As a result, newly inserted data never shows up while enumerating the group.

[robbiehanson]

I understand that you need an 'object' to call the YapCollectionsDatabaseViewGroupingWithObjectBlock

You also need a 'metadata' object to call YapCollectionsDatabaseViewGroupingWithMetadataBlock. So that wouldn't work either. Because when setting primitiveMetadata, you're just passing NSData.

Due to some optimizations, in my code am storing objects by archiving them myself and then calling
setPrimitiveData: forKey: withPrimitiveMetadata: instead of setObject:...

The basic premise of YapDatabase is to deal with objects, and let the archiving happen automatically. The primitive methods allow you to essentially opt out of the YapDatabase architecture (including caching & extensions) for those situations in which you want to store something in the sqlite database, but don't really want to include the something in the greater YapDatabase stuff. Thus when you use the setPrimitive::: method, none of the extensions will see it.

Can you give me a little more information about the optimizations you're referring to. Maybe we can come up with a more elegant solution, either on YapDatabase side, or on the app side.

[chaitanyapandit]

Sure, some of my objects have 20-30 properties which include thumbnail images converted to data. Since I’m saving those in a background thread, I create their copies.

Now since eventually those objects get archived I could eliminate the copy step by archiving it myself and setting it as primitive data in YAP, and while reading YAP will return it as the object itself since I converted it to NSData by archiving.

BTW full text search is a killer feature! Took me < 3 min to integrate :)

On 04-Dec-2013, at 2:24 am, Robbie Hanson notifications@github.com wrote:

Can you give me a little more information about the optimizations you're referring to. Maybe we can come up with a more elegant solution, either on YapDatabase side, or on the app side.

[robbiehanson]

Since I’m saving those in a background thread, I create their copies.

I'm not sure I understand. Why do you have to copy the object in order to write it to the database on a background thread? Are you making modifications to the object on the UI thread?

[chaitanyapandit]

Yup, that's why, modify some mutable properties.

On 05-Dec-2013, at 12:10 AM, Robbie Hanson notifications@github.com wrote:

Are you making modifications to the object on the UI thread?

—
Reply to this email directly or view it on GitHub.

[robbiehanson]

I'm still thinking about this issue. I'm trying to come up with an elegant yet flexible solution. Here's what I'm thinking:

I could add a method that allows you to pass:

• object (optional)
• primitiveObjectData (optional, pre-serialized)
• metadata (optional)
• primitiveMetadataData (optional, pre-serialized)
• options

The options will allow you to specify:

• should cache object (if not nil)
• should cache metadata (if not nil)
• should forward to extensions

And the extensions will get support for this method, and can act properly based on whether the object and/or metadata is non-nil, and whether the extension needs the object and/or metadata.

So this method will allow you to pre-serialize, and still include in extensions (you just need to pass the metadata obj since the extension you're using requires the metadata).

The method will also allow devs to add stuff to the database but skip the cache.

Thoughts? Would this work for you?

[robbiehanson]

There's a new method you can use to pass an existing version of the pre-serialized object:

- (void)setObject:(id)object forKey:(NSString *)key inCollection:(NSString *)collection
                                                    withMetadata:(id)metadata
                                                serializedObject:(NSData *)preSerializedObject
                                              serializedMetadata:(NSData *)preSerializedMetadata;