You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the while and do...while loops, continue statement causes the program control pass to the conditional test - 'conflict' which is initialized to NO and never changed elsewhere.
BOOL conflict = NO;
int attempts = 0;
do {
attempts++;
NSAssert1(attempts < 100, @"FCModel subclass %@ is not returning usable, unique values from primaryKeyValueForNewInstance", NSStringFromClass(self.class));
id newKeyValue = [self.class primaryKeyValueForNewInstance];
if ([self.class instanceFromDatabaseWithPrimaryKey:newKeyValue]) continue; // already exists in database
[self setValue:newKeyValue forKey:key];
} while (conflict);
The text was updated successfully, but these errors were encountered:
As repo is alive and I see you'r ignoring this bug from commit to commit, try running this peace of code, maybe that will convince you to fix it and save anyone else from hassle of finding out why app crashes in production environment due to sqlite unique pk constraint with large amount of records.
BOOL conflict = NO;
do {
continue;
} while (conflict);
For the while and do...while loops, continue statement causes the program control pass to the conditional test - 'conflict' which is initialized to NO and never changed elsewhere.
The text was updated successfully, but these errors were encountered: