[BREAKGLASS] Append-only mirror of github.com/signalapp/YapDatabase
Go to file
2016-09-07 17:49:17 -07:00
Examples Fixing Xcode projects (due to filename change in previous commit). 2016-09-07 17:49:17 -07:00
Framework Adding watchOS build for Carthage. 2016-09-07 16:28:55 -07:00
Testing Fixing Xcode projects (due to filename change in previous commit). 2016-09-07 17:49:17 -07:00
YapDatabase Workaround for CocoaPods v1 bug. Fixes issue #322. 2016-09-07 17:46:48 -07:00
YapDatabase.xcodeproj Fixing Xcode projects (due to filename change in previous commit). 2016-09-07 17:49:17 -07:00
.gitignore Adding Carthage stuff to .gitignore 2015-10-16 16:30:56 -07:00
.travis.yml Update travis.yml to use Xcode 7 2015-10-27 11:43:04 -07:00
Cartfile Fixing tvOS build for Carthage & CocoaPods+Swift. 2016-09-01 14:10:32 -07:00
Cartfile.resolved Fixing tvOS build for Carthage & CocoaPods+Swift. 2016-09-01 14:10:32 -07:00
LICENSE.txt Added license file 2013-04-07 21:18:41 -07:00
README.md Update README.md 2016-04-02 09:34:15 -07:00
YapDatabase.podspec Fixing podspec to work with CocoaPods v1. It wouldn't "lint" in it's previous form, and thus couldn't be pushed. 2016-09-07 15:13:19 -07:00

YapDatabase

Build Status Pod Version Carthage compatible

YapDatabase is a "key/value store and MUCH MORE" built atop sqlite for iOS & Mac. It has the following features:

  • Concurrency. You can read from the database while another thread is simultaneously making modifications to the database. So you never have to worry about blocking the main thread, and you can easily write to the database on a background thread. And, of course, you can read from the database on multiple threads simultaneously.

  • Built-In Caching. A configurable object cache is built-in. Of course sqlite has caching too. But it's caching raw serialized bytes, and we're dealing with objects. So having a built-in cache means you can skip the deserialization process, and get your objects much faster.

  • Collections. Sometimes a single key isn't enough. Sometimes a collection & key is better. No worries. YapDatabase supports collections out of the box.

  • Metadata. Ever wanted to store extra data along with your object? Like maybe a timestamp of when it was downloaded. Or a fully separate but related object? You're in luck. Metadata support comes standard. Along with its own separate configurable cache too!

  • Views. Need to filter, group & sort your data? No problem. YapDatabase comes with Views. And you don't even need to write esoteric SQL queries. Views work using blocks with your own code. Plus they automatically update themselves, and they make animating tables super easy.

  • Secondary Indexing. Speed up your queries by indexing important properties. And then use SQL style queries to quickly find your items.

  • Full Text Search. Built atop sqlite's FTS module (contributed by google), you can add extremely speedy searching to your app with minimal effort.

  • Relationships. You can setup relationships between objects and even configure cascading delete rules.

  • Sync. Support for syncing with Apple's CloudKit is available out of the box. There's even a fully functioning example project that demonstrates writing a syncing Todo app.

  • Extensions. More than just a key/value store, YapDatabase comes with an extensions architecture built-in. You can even create your own extensions.

  • Performance. Fetch thousands of objects on the main thread without dropping a frame.

  • Objective-C. A simple to use Objective-C API means you'll be up and running in no time.


See what the API looks like in "hello world" for YapDatabase
Learn more by visiting the wiki