martydill/ios-queryable

ios-queryable is an implementation of IQueryable/IEnumerable for Core Data

ios-queryable's Issues

update cocoapods to reflect recent changes

Hey there, any chance you could add another tag to cocoapods to get the most recent version of this up there?

Cool library!

Semantic Versioning

I’ve recently added IOSQueryable to the CocoaPods package manager repo.

CocoaPods is a tool for managing dependencies for OSX and iOS Xcode projects and provides a central repository for iOS/OSX libraries. This makes adding libraries to a project and updating them extremely easy and it will help users to resolve dependencies of the libraries they use.

However, IOSQueryable doesn't have any version tags. I’ve added the current HEAD as version 0.0.1, but a version tag will make dependency resolution much easier.

Semantic version tags (instead of plain commit hashes/revisions) allow for resolution of cross-dependencies.

In case you didn’t know this yet; you can tag the current HEAD as, for instance, version 1.0.0, like so:

$ git tag -a 1.0.0 -m "Tag release 1.0.0"
$ git push --tags

A few tests failed in 64 bits with iOS7.1.

A few tests failed in 64 bits with iOS7.1.

FirstOrDefault with condition throws exception on line #139 - Bad Access

As I understand it, these two code snippets should be identical in behaviour.

[[myQueryable where:@"someId = %@", someId] firstOrDefault];
and
[myQueryable firstOrDefault:@"someId = %@", someId];

However the first works a treat, the second dies in the where [NSPredicate predicateWithFormat:condition arguments:args];

queryable Take:1] singleOrDefault] throws exception for multiple results

I assume this is unintended behaviour, I hadn't expected it.

Great project though.

countByEnumeratingWithState:objects:count: crashes if managed context changes while enumerated

The method in discussion executes a fetch request (via its toArray) each time the runtime asks for a batch of objects to enumerate through. And if the managed object contents change between fetch requests, it generates a crash as the toArray contents are not the same between invocations.

Unrecognized Selector count sent to an NSNumber

While trying to query an average value during an NSManagedObject's awakeFromFetch and awakeFromInsert, I'm getting this error:

2015-08-10 22:07:10.077 PropertyHunter[29805:971191] -[NSDecimalNumber count]: unrecognized selector sent to instance 0x608000431260

The line of code:

[[[sharedContext ofType:@"Store"] where:@"location.zipcode = %@", self.zipcode] average:@"visits"];

I'm using this in a Mac OS X app. Any idea why this happens?