mirror of
https://github.com/darlinghq/fmdb.git
synced 2024-11-30 07:50:27 +00:00
Update comments for online documentation
This commit is contained in:
parent
cb92845077
commit
1da3a20b00
@ -690,11 +690,9 @@ typedef NS_ENUM(int, FMDBCheckpointMode) {
|
||||
an exclusive transaction, not a deferred transaction. This behavior
|
||||
is likely to change in future versions of FMDB, whereby this method
|
||||
will likely eventually adopt standard SQLite behavior and perform
|
||||
deferred transactions.
|
||||
|
||||
If you really need exclusive tranaction, it is recommended that you
|
||||
use `beginExclusiveTransaction`, instead, not only to make your intent
|
||||
explicit, but also to future-proof your code.
|
||||
deferred transactions. If you really need exclusive tranaction, it is
|
||||
recommended that you use `beginExclusiveTransaction`, instead, not
|
||||
only to make your intent explicit, but also to future-proof your code.
|
||||
|
||||
*/
|
||||
|
||||
|
@ -206,11 +206,9 @@ NS_ASSUME_NONNULL_BEGIN
|
||||
an exclusive transaction, not a deferred transaction. This behavior
|
||||
is likely to change in future versions of FMDB, whereby this method
|
||||
will likely eventually adopt standard SQLite behavior and perform
|
||||
deferred transactions.
|
||||
|
||||
If you really need exclusive tranaction, it is recommended that you
|
||||
use `inExclusiveTransaction`, instead, not only to make your intent
|
||||
explicit, but also to future-proof your code.
|
||||
deferred transactions. If you really need exclusive tranaction, it is
|
||||
recommended that you use `inExclusiveTransaction`, instead, not only
|
||||
to make your intent explicit, but also to future-proof your code.
|
||||
*/
|
||||
|
||||
- (void)inTransaction:(__attribute__((noescape)) void (^)(FMDatabase *db, BOOL *rollback))block;
|
||||
|
@ -210,11 +210,9 @@ NS_ASSUME_NONNULL_BEGIN
|
||||
an exclusive transaction, not a deferred transaction. This behavior
|
||||
is likely to change in future versions of FMDB, whereby this method
|
||||
will likely eventually adopt standard SQLite behavior and perform
|
||||
deferred transactions.
|
||||
|
||||
If you really need exclusive tranaction, it is recommended that you
|
||||
use `inExclusiveTransaction`, instead, not only to make your intent
|
||||
explicit, but also to future-proof your code.
|
||||
deferred transactions. If you really need exclusive tranaction, it is
|
||||
recommended that you use `inExclusiveTransaction`, instead, not only
|
||||
to make your intent explicit, but also to future-proof your code.
|
||||
|
||||
*/
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user