I added some custom fields in my User class and I would like to hide some of them to the users like the password and verifiedEmail ones.
Is there a way to do this?
When querying an object, you can specify which fields should be returned by using the selectKeys method.
Here is an example for iOS:
PFQuery *query = [PFQuery queryWithClassName:#"GameScore"];
[query selectKeys:#[#"playerName", #"score"]];
[query findObjectsInBackgroundWithBlock:^(NSArray *results, NSError *error) {
// objects in results will only contain the playerName and score fields
}];
And one for Android:
ParseQuery<ParseObject> query = ParseQuery.getQuery("GameScore");
query.selectKeys(Arrays.asList("playerName", "score"));;
List<ParseObject> results = query.find();
If you're developing on another platform, consult the relevant documentation for the one you use (https://www.parse.com/docs/).
Related
Im trying to implement a search bar using PFQueryTableView.
I can successfully retrieve objects that are inside a class with no pointer column with this code:
- (PFQuery *)queryForTable {
PFQuery *query;
if (self.canSearch == 0) {
query = [PFQuery queryWithClassName:self.parseClassName];
} else {
query = [PFQuery queryWithClassName:self.parseClassName];
NSString *searchThis = [searchedBar.text lowercaseString];
#warning key you wanted to search here
[query whereKey:#"colors" containsString:searchThis];
}
[query orderByAscending:#"colors"];
But when I use this same query to search objects in a column that is in the same Class that have another column Pointer<_User> the query doesn't work anymore.
What should I change in the code above to query that column(with no Pointer) that exists inside a Class with a pointer column ?
Thanx and cheers!
Check out my answer here : Having trouble passing PFUser as a PFObject
I think this is what your looking for. It involves accessing PFObjects within PFObjects
I have a user , activty, photo class. Where user likes other users Attached screenshot of Activity Class https://dl.dropboxusercontent.com/u/33860877/Activity.png
My problem is that when a user likes more than 1000, the limitation on the "filter likes" query will cause below method to get users that the user has already liked because number of activity (likes) more than 1000. What should be done here to avoid this?
-(void) loaddata {
PFQuery *filterUsers = [PFUser query];
[filterUsers whereKey:kMUParseUserAccountStatus equalTo:#"Active"];
filterUsers.limit =1000;
PFQuery *filterLikes = [[PFQuery alloc] initWithClassName:kMUActivityClassKey];
[filterLikes whereKey:kMUActivityUserFromKey equalTo:[PFUser currentUser]];
filterLikes.limit =1000;
PFQuery *query = [[PFQuery alloc] initWithClassName:kMUPhotoClassKey];
[query whereKey:kMUPhotoUserKey notEqualTo:[PFUser currentUser]];
[query whereKey:kMUPhotoPicturePriorityKey equalTo:#(0)];
[query whereKey:kMUPhotoUserKey matchesQuery:filterUsers];
[query whereKey:kMUPhotoUserKey doesNotMatchKey:kMUActivityUserToKey inQuery:filterLikes];
[query includeKey:kMUPhotoUserKey];
[query findObjectsInBackgroundWithBlock:^(NSArray *objects, NSError *error) {
if(!error)
{
if(objects.count>0)
{
[self updateInformation];
}
else
{
if(objects.count==0)
{
self.hasMorePhotos = false;
}
}
}
}];
}
You need to work around the 1000 record limit.
If I understand you correctly, you want to show photos that the current user HAS NOT YET LIKED. Your solution is not efficient, as you compare a key in a query of 1000 objects (or, if the limit was not 1000, your solution would perhaps need to compare thousands of objects).
If you need to filter out liked photos, you could instead store an array of objectIDs on the user. When the user likes a photo, you could add this objectId to an array on the User object, or another object tied to the user. Then, in your query, you could compare with this array rather than another query:
[query whereKey:#"objectId" notContainedIn:arrayOfLikedObjectIds];
I have these entities:
ProductsEntity
name
orders [ProductsOrderRelationship]
OrderEntity
products [ProductsOrderRelationship]
ProductsOrderRelationship
order [OrderEntity]
product [ProductsEntity]
quantity
Now, I want to edit an existing order. I have a list of products available and cart.
Now I want to add these available products to the cart.
The code must check if the products exist, so it only increases the quantity.
But, by now, it is simply adding more relationships..
Let me share a piece of code!
The interface has a list on the left with the available products and a list on the right with the cart (order entity). Both have array controllers linked to my code. Then I have this action:
- (IBAction)addSelectedProducts:(id)sender {
NSArray *firstSelectedProducts = [availableProductsController selectedObjects];
//Objects selected in the array controller
NSMutableArray *selectedProducts = [[NSMutableArray alloc] initWithCapacity:1];
//Here I will filter the repeated ones
NSMutableSet *newProducts = [NSMutableSet set];
//This is the final value to change in the current order entry.
NSMutableSet *oldProducts = [orderManagedObject valueForKey:#"products"];
//This is the old value I will change.
//Here we filter every repeated entries:
if ( [firstSelectedProducts count] > 0 ) {
for (id object in firstSelectedProducts) {
if (![oldProducts containsObject:object]) {
[selectedProducts addObject:object];
}
}
}
//Here we create objects in the relationship entity:
for (int i = 0; i < [selectedProducts count]; i++) {
// Create new relationship.
NSManagedObject *newProductObject = [
NSEntityDescription
insertNewObjectForEntityForName:#"ProductsOrderRelationship"
inManagedObjectContext:managedObjectContext
];
[newProductObject setValue:[selectedProducts objectAtIndex:i] forKey:#"product"];
[newProductObject setValue:orderManagedObject forKey:#"order"];
[newProducts addObject:newProductObject];
[newProductObject release];
}
[newProducts unionSet:oldProducts];
//Join old products and new products.
[orderManagedObject setValue:newProducts forKey:#"products"];
//Re-set the value.
//(... release stuff here)
}
I can't find a guide to this specific problem.. Any suggestions?
I'm guessing that firstSelectedProducts contains ProductsEntity objects and oldProducts contains ProductsOrderRelationship objects. If that's true, the problem is that...
if (![oldProducts containsObject:object]) {
...will never match anything.
(What you call ProductsOrderRelationship is often called a LineItem. Changing the name of the class and its associated variables might make the logic clearer.)
I currently have a cardType attribute on my entity, which in the old model could be "Math", "Image" or "Text". In the new model, I'll be using just "Math" and "Text" and also have a hasImage attribute, which I want to set to true if the old cardType was Image (which I want to change to "Text").
Lastly, I have a set of another entity, "card", of which a set can be associated with a deck, and in each of those, I'll also have hasImage which I want to set to true if the deck was of "Image" type before.
Is this all possible using the Value Expression in the Mapping Model I've created between the two versions, or will I have to do something else?
I can't find any document telling me exactly what is possible in the Value Expression (Apple's doc - http://developer.apple.com/library/mac/#documentation/cocoa/conceptual/CoreDataVersioning/Articles/vmMappingOverview.html%23//apple_ref/doc/uid/TP40004735-SW3 - only has a very simple transformation). If I have to do something else, what would that be? This seems simple enough that an expression should be able to do it.
One thing you can do is create a custom migration policy class that has a function mapping your attribute from the original value to a new value. For example I had a case where I needed to map an entity called MyItems that had a direct relationship to a set of values entities called "Items" to instead store an itemID so I could split the model across multiple stores.
The old model looked like this:
The new model looks like this:
To do this, I wrote a mapping class with a function called itemIDForItemName and it was defined as such:
#interface Migration_Policy_v1tov2 : NSEntityMigrationPolicy {
NSMutableDictionary *namesToIDs;
}
- (NSNumber *) itemIDForItemName:(NSString *)name;
#end
#import "Migration_Policy_v1tov2.h"
#implementation Migration_Policy_v1tov2
- (BOOL)beginEntityMapping:(NSEntityMapping *)mapping manager:(NSMigrationManager *)manager error:(NSError **)error {
namesToIDs = [NSMutableDictionary dictionaryWithObjectsAndKeys:[NSNumber numberWithInt:1],#"Apples",
[NSNumber numberWithInt:2],#"Bananas",
[NSNumber numberWithInt:3],#"Peaches",
[NSNumber numberWithInt:4],#"Pears",
[NSNumber numberWithInt:5],#"Beef",
[NSNumber numberWithInt:6],#"Chicken",
[NSNumber numberWithInt:7],#"Fish",
[NSNumber numberWithInt:8],#"Asparagus",
[NSNumber numberWithInt:9],#"Potato",
[NSNumber numberWithInt:10],#"Carrot",nil];
return YES;
}
- (NSNumber *) itemIDForItemName:(NSString *)name {
NSNumber *iD = [namesToIDs objectForKey:name];
NSAssert(iD != nil,#"Error finding ID for item name:%#",name);
return iD;
}
#end
Then for the related Mapping Name for the attribute in your mapping model you specify the Value Expression as the result of your function call as such:
FUNCTION($entityPolicy,"itemIDForItemName:",$source.name) **
You also have to set the Custom Policy Field of your Mapping Name for that attribute to your mapping class name (in this case Migration_Policy_v1tov2).
**note this should match the selector signature of the method
Imagine an CoreData entity (e.g. named searchEngine).
NSManagedObjectContext manages some "instances" of this entity.
The end-user is going to be able to select his "standard searchEngine" with a NSPopupButton.
The selected object of NSPopupButton should be binded to the NSUserDefaults.
The problem:
1) #try{save}
a) If you try to save the selected "instance" directly to NSUserDefaults there comes something like this:-[NSUserDefaults setObject:forKey:]: Attempt to insert non-property value ' (entity: searchEngine; id: 0x156f60 ; data: {
url = "http://google.de/";
someAttribute = 1;
name = "google";
})' of class 'searchEngine'.
b) If you try to convert the "instance" to NSData comes this:-[searchEngine encodeWithCoder:]: unrecognized selector sent to instance 0x1a25b0
So any idea how to get this entities in a plist-compatible data?
2) #try{registerDefaults}
Usually the registerDefaults: method is implemented in + (void)initialize. The problem here is that this method is called before CoreData loads the saved entities from his database. So I can't set a default to a no-existing object, right?
I know, long questions... but: try{[me provide:details]} ;D
If you need to store a reference to a specific managed object, use the URI representation of its managed object ID:
NSURL *moIDURL = [[myManagedObject objectID] URIRepresentation];
You can then save the URL to user defaults.
To retrieve the managed object, you use:
NSManagedObjectID *moID = [myPersistentStoreCoordinator managedObjectIDForURIRepresentation:moIDURL];
NSManagedObject *myManagedObject = [myContext objectWithID:moID];
The only caveat is that you must ensure that the original managed object ID is permanent -- this is not a problem if you've already saved the object, alternatively you can use obtainPermanentIDsForObjects:error:.
Here's the cleanest and shortest way to currently do this using the setURL and getURL methods added in 4.0 to avoid extra calls to NSKeyedUnarchiver and NSKeyedArchiver:
Setter:
+ (void)storeSomeObjectId:(NSManagedObjectID *)objectId
{
[[NSUserDefaults standardUserDefaults] setURL:[objectId URIRepresentation]
forKey:#"someObjectIdKey"];
[[NSUserDefaults standardUserDefaults] synchronize];
}
Getter:
+ (SomeManagedObject *)getObjectByStoredId
{
NSURL *uri = [[NSUserDefaults standardUserDefaults] URLForKey:#"someObjectIdKey"];
NSManagedObjectID *objectId = [self.persistentStoreCoordinator managedObjectIDForURIRepresentation:uri];
SomeManagedObject *object = [self.managedObjectContext objectWithID:objectId];
}
You wouldn't want to try and archive a core data entity and store it. Instead, you would store the key or some other known attribute and use it to fetch the entity when the application starts up.
Some example code (slightly modified from the example posted in the Core Data Programming Guide):
NSManagedObjectContext *moc = [self managedObjectContext];
NSEntityDescription *entityDescription = [NSEntityDescription
entityForName:#"SearchEngine" inManagedObjectContext:moc];
NSFetchRequest *request = [[[NSFetchRequest alloc] init] autorelease];
[request setEntity:entityDescription];
NSPredicate *predicate = [NSPredicate predicateWithFormat:
#"engineName LIKE[c] '%#'", selectedEngineName];
[request setPredicate:predicate];
NSError *error = nil;
NSArray *array = [moc executeFetchRequest:request error:&error];
if (array == nil)
{
// Deal with error...
}
This way you save the name in the user defaults and fetch the entity when necessary.
My model saves the record's UUID to the UserDefaults in order to launch the last opened record in the next app launch.
public class Patient: NSManagedObject {
override public func awakeFromInsert() {
super.awakeFromInsert()
uuid = UUID()
}
extension Patient {
#NSManaged public var uuid: UUID
#NSManaged ...
}
It is a good practice to identify each record with an unique ID (UUID). You can save the UUID as string simply calling uuid.uuidString.