diff options
author | August Mueller <gus@flyingmeat.com> | 2014-10-28 19:19:19 +0300 |
---|---|---|
committer | August Mueller <gus@flyingmeat.com> | 2014-10-28 19:19:19 +0300 |
commit | e41c62f7faee65bccd1da219235e2403c93ed3a1 (patch) | |
tree | 539ca4eff4ceeffdb0c9d38754a827bd3ec02c10 | |
parent | 79679e59bb7e4f782ba886ad93a11b1be46add5a (diff) |
Removed some inaccuracies from the docs.
-rw-r--r-- | README.markdown | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/README.markdown b/README.markdown index 0947c26..32c4241 100644 --- a/README.markdown +++ b/README.markdown @@ -72,7 +72,7 @@ Executing updates returns a single value, a `BOOL`. A return value of `YES` mea A `SELECT` statement is a query and is executed via one of the `-executeQuery...` methods. -Executing queries returns an `FMResultSet` object if successful, and `nil` upon failure. Like executing updates, there is a variant that accepts an `NSError **` parameter. Otherwise you should use the `-lastErrorMessage` and `-lastErrorCode` methods to determine why a query failed. +Executing queries returns an `FMResultSet` object if successful, and `nil` upon failure. You should use the `-lastErrorMessage` and `-lastErrorCode` methods to determine why a query failed. In order to iterate through the results of your query, you use a `while()` loop. You also need to "step" from one record to the other. With FMDB, the easiest way to do that is like this: |