Setting a database option results in a commit being performed.
Using this method while a transaction is active may cause unpredictable results and is not recommended. The call changes the
isolation level of the connection, but does not update the ULTransaction.IsolationLevel value.
Recognized options are:
The value used for global autoincrement columns. The value must be in the range [0,System.UInt32.MaxValue]. The default is
the ULConnection.INVALID_DATABASE_ID value (used to indicate that the database ID has not been set for the current database).
The value used to control the degree to which the operations in one transaction are visible to the operations in other concurrent
transactions. The value must be one of "read_uncommitted" or "read_committed". The default is "read_committed". Setting the
isolation_level on a connection to "read_uncommitted" is equivalent to wrapping all operations on that connection with BeginTransaction(System.Data.IsolationLevel.ReadUncommitted)
and Commit() calls. Similarly, "read_committed" is equivalent to System.Data.IsolationLevel.ReadCommitted. SetDatabaseOption()
should not be used to set the current transaction's isolation level; use BeginTransaction(IsolationLevel) instead. UltraLite's
definition of each isolation level is slightly different than ADO.NET's documentation of IsolationLevel. This value is set
on a per connection basis.
The value used for identifying the database during synchronization. Use a null reference (Nothing in Visual Basic) as the
value to remove the ml_remote_id option from the database.