ZipZap VS GRDB.swift

ZipZap - zip file I/O library. Language: Objective-C.

Streaming zip file is going to have issues when compression ratio is not 0 for some implementations (such as ZipFileStream from Java / Android). I fixed this a few years ago for ZipZap: https://github.com/pixelglow/ZipZap/pull/155

Particularly, the local header (per file) is written before the file content, and you cannot get accurate compressed size prior to actual compression. Central file header is at the end of the file, so there is no problem to get accurate compressed size, but some zip reader implementations (such as ZipFileStream) cannot use central file header (because it is at the end), and will use the wrong compressed size.

I'm using GRDB , you can use existing pre-populated sqlite DB file. https://github.com/groue/GRDB.swift/wiki/Performance .

Not quite exactly sure what you mean but if its a .sqlite3 file then you can use it with this easy to use library https://github.com/groue/GRDB.swift

The 3rd party library I use GRDB SwiftyUserDefaults Kingfisher SwiftDate Popovers

The other thing is that it could be an overkill for your app if you just need to basically "store an array of 100 objects". Then you could probably consider other solutions like SQLite (with wrappers like GRDB) or plain JSON files.

https://github.com/groue/GRDB.swift#readme https://github.com/groue/GRDB.swift/tree/master/Documentation https://swiftpackageindex.com/groue/grdb.swift/documentation/grdb/

https://github.com/groue/GRDB.swift/blob/master/Documentation/AssociationsBasics.md might be interesting to look at for how it handles relationships between entities.

I recently used GRDB.

Check the performance comparison page. GRDB comes with a convenient and ready-made support for Swift Codable that performs quite well. When needed, it is possible to write less convenient but optimized record types that add very little overhead to SQLite, and perform really well.

Hey all. So I just got done developing an app that does visitation tracking. Basically the user creates an account with email, name, password etc.. the info is then saved to a SQLite database (using GRDB) with a table named "User" and then injected into the next view controller and so on... I plan on allowing the user to store their account in icloud in the future.