Reset architectures setting to default in iOS targets to avoid lack of ARM7s build, which causes linker error when building an app.
Updated the error message for other linker flag
Corrected the linker error message
These require the ?include_deleted support I just added to TouchDB.
If the app calls -DELETE on a CouchDatabase, the object needs to forget its current state, like the document cache and change-tracker.
Required to avoid breaking with the latest TouchDB commit (9dbdaf8).
When CouchTouchDBDatabase gets a new-revision notification from TouchDB, it needs to check whether this is the winning revision of the document; otherwise it shouldn't post it or CouchDocument will get confused. (This is another case of bug TouchDB-152, which just happens to live in CouchCocoa.) Note: This is a dependency on a pretty new revision of TouchDB from earlier this week.
document should always choose the highest revision as current revision
The following now work, in Xcode 4.4+: server[@"dbname"] db[@"doc_id"] doc[@"property"] rev[@"property"]
-[CouchDatabase untitledDocument] now just generates a new UUID for the doc. Having docs without IDs complicated doc-ID caching and made it too difficult to enforce having only one CouchDocument instance per document ID. Fixes <couchbaselabs/TouchDB-iOS#140>
Don't make CouchCocoa calls on the TouchDB thread!
Requires the corresponding TouchDB commit that I just pushed.
(This is to stay in sync with the corresponding change in TouchDB that added a parameter to TDFilterBlock.)
by using the TDReplicator static methods. The usage of these statics is done dynamically so as to not require a link time dependency on TouchDB. (Modified/simplified by Jens.)
Now using Objective-C runtime imp_implementationWithBlock function to avoid the overhead of computing the property name from the method selector on every call. Should make property access a lot faster!
In the log message in -[RESTOperation wait], identify the operation as well as the time spent.
CouchQuery stores error of the last request
With TouchDB a database can detect changes by just observing NSNotifications from the TDDatabase, instead of having to run a TDChangeTracker and open a URLConnection. Change-Id: I3ae7fc2b9ad788db784bd6e2beb637023898c7eb