Dr. Mickey Lauer

@noremac Thanks for your comment. The thing is… I welcome fine granular subprojects, if, and only if, they make a difference with regards to the amount of, say, linked libraries,...

I have renamed the package as discussed. The Objective-C part can now be used via `import YapDatabase`. https://github.com/mickeyl/SwiftYapDatabase/commit/e1befb00a014fa75721633950e100dddd343f496

FWIW, for now I settled on using https://github.com/groue/GRDB.swift. I still miss YapDatabase's approach with the computed views, but while YapDatabase seems to be EOL, GRDB is Swift-native and embraces Combine...

Indeed – I'm pretty sure this would be possible. I would have started already, but I'm just worried about Apple presenting their own Swift-native database solution soon… so lets wait...

I have been working around this by using dedicated consecutive searches for every single property – which is probably less performant, but I don't see another way. It looks like...

This is a great idea. I'd definitely make use of that. Did you have the chance to work on that yet?

Any updates here?

Ok, I guess I'm stumbling at the same issue as you. I have created the following simple patch: ``` diff --git a/YapDatabase/YapDatabase.m b/YapDatabase/YapDatabase.m index 5957fe8..e95fcbd 100644 --- a/YapDatabase/YapDatabase.m +++ b/YapDatabase/YapDatabase.m...

Did anything happen with regards to this bug yet? I'm working on a song book, having a song database where the song metadata contains a timestamp for 'last recently played'....

I'm using the above patch now. It's probably still heavier than it would have to be (since after all I only change the sorting group), but it's still better IMHO...