Databases
StackOverflow2013
Postsdbo
POSaving to database using FMDB crashes on interpreting NSInteger
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSaving to database using FMDB crashes on interpreting NSInteger
    primarykey
    data
    text
    <p>When the below function is called, I get the EXC_BAD_ACCESS crash. It looks like FMDB is having a problem interpreting the subject_id NSInteger as it makes it through the two NStrings and bombs when it hits this subject_id column in the WHERE clause. </p> <pre><code>- (void) saveAllData { if(isDirty) { DrillDownAppAppDelegate *appDelegate = (DrillDownAppAppDelegate *)[[UIApplication sharedApplication] delegate]; FMDatabase *database = [FMDatabase databaseWithPath:appDelegate.getDBPath]; if ([database open]) { [database executeUpdate:@"update Subject Set subject = ?, category = ? where subject_id = ?", self.title, self.category_title, self.subject_id]; [database close]; } isDirty = NO; } //Reclaim all memory here. [title release]; title = nil; [category_title release]; category_title = nil; } </code></pre> <p>The problem is the same as I ran into in another post on FMDB insert problems and this boils down to something wrong with my subject_id member. I believe I am using a wrong declaration in the header. Here it is: </p> <pre><code>// // Subject.h // DrillDownApp #import &lt;UIKit/UIKit.h&gt; @interface Subject : NSObject { NSInteger subject_id; NSString *category_title; NSString *title; // NSMutableArray *quotes; BOOL isDirty; // BOOL isDetailViewHydrated; } - (id) initWithPrimaryKey:(NSInteger)pk; @property (nonatomic, readwrite) BOOL isDirty; //@property (nonatomic, readwrite) BOOL isDetailViewHydrated; - (void) addSubject; - (NSInteger)getNextSubjectId; @property (nonatomic, assign) NSInteger subject_id; @property (nonatomic, copy) NSString * title; @property (nonatomic, copy) NSString * category_title; //@property (nonatomic, retain) NSMutableArray *quotes; //- (void) saveAllData; @end </code></pre> <p>(Note: I edited this majorly as I figured out the rest of it.)</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USjroyce
    1. USjroyce
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSaving to database using FMDB crashes on interpreting NSInteger
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POSaving to database using FMDB crashes on interpreting NSInteger
      1. USchancyWu
      1. VTFavorite
    1. COYou are setting title value and category title value to the Subject object. But where you are saving the object to the database?
      singulars
      1. POSaving to database using FMDB crashes on interpreting NSInteger
      1. USIlanchezhian
    2. COI updated this to include the saveAllData function that saves the object to the database. But the problem is it doesn't even make it there as the data doesn't stay with the object. I think my problem is that I am not calling the setTitle and setCategory_Title function correctly as these methods never get touched when running in debugger...
      singulars
      1. POSaving to database using FMDB crashes on interpreting NSInteger
      1. USjroyce
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload