diff options
author | 尊敬的伊露维塔 <42320822+Token-LiMing@users.noreply.github.com> | 2020-10-11 20:16:18 +0300 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-10-11 20:16:18 +0300 |
commit | 7f7ca2d685589527b581beb3b4dbb55fa30d57fc (patch) | |
tree | 2b7eea558ddf7f530e3d4e98316f612f3d4b2b4e | |
parent | 2ca2cad644ae9d2bfc5584983b04807b09a443b2 (diff) |
Update example code for FMResultSet
We recently discovered _sqlite3DbMallocRawNN crash, MACH_Exception EXC_BAD_ACCESS KERN_INVALID_ADDRESS fault_address:0x3037646236307474.
And we find a commit: 7da3c812cdddd6f5da1df31e7751ef3e56dacd6b. This commit update documentation for FMResultSet.
I suggest to update example code for FMResultSet. If the user did not read the newest documentation, they can read example code and avoid making mistakes.
-rw-r--r-- | README.markdown | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/README.markdown b/README.markdown index b943592..abf0cc5 100644 --- a/README.markdown +++ b/README.markdown @@ -241,6 +241,7 @@ FMResultSet *s = [db executeQuery:@"SELECT COUNT(*) FROM myTable"]; if ([s next]) { int totalCount = [s intForColumnIndex:0]; } +[s close]; // If you cannot confirm whether the result set is exhausted, you will need to call the -close method on the FMResultSet for safety. ``` `FMResultSet` has many methods to retrieve data in an appropriate format: |