Chris Ballinger

This may be already addressed by the preprocessor check to see if both YapDatabase and YapDatabase/SQLCipher subspecs are used at the same time.

I think Robbie was thinking about building a common foundation as well, and then refactor SearchResultsView to use that On Tue, Aug 25, 2015 at 11:30 AM, toolboxash [email protected] wrote:...

Yeah it would be useful for the RTreeIndex as well On Tue, Aug 25, 2015 at 1:26 PM, toolboxash [email protected] wrote: > I would really like to see it implemented...

YapDatabase doesn't really have a strong opinion on how your objects are serialized or deserialized. By default it uses NSKeyedArchiver/Unarchiver but you can set your own custom (de)serializers that don't...

Ah good call. The newer method `archivedData(withRootObject:requiringSecureCoding:)` wasn't introduced until iOS 11, but YapDB still supports down to iOS 8.2. Changing the default serializers to require secure coding would be...

Why are you opening it like that? I'm a little confused. I think maybe this is what you're looking for: https://github.com/yapstudios/YapDatabase/blob/e05584ad54b827844866e840cb4aa0ffbe14a6f3/YapDatabase/YapDatabaseOptions.h#L157 Once you can open the database the usual way,...

Why not keep the dependency until enough users have migrated?

I can preliminarily verify that this patch resolves the crashes I was seeing from end users.

Swift value types cannot respond to Obj-C selectors. I think there was an attempt by @robbiehanson to fix this bridging issue, but it looks like there are still some rough...

Yeah I agree, structs are awesome when it comes to modeling data. Although I still really like YapDatabase, I've been reaching for [GRDB](https://github.com/groue/GRDB.swift) lately which has some very similar qualities....