System.Data.SQLite
Check-in [45cc5a21fa]
Not logged in

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Update a statement in the provider limitations documentation regarding deferred transaction locking semantics. Fix for [425f060dec].
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: 45cc5a21fa9a4337b19b5bf607c5f8c4618d2617
User & Date: mistachkin 2014-07-02 17:45:06
References
2014-07-02
17:46 Closed ticket [425f060dec]: Documentation update - "Limitations of ..." plus 4 other changes artifact: 624c6b5775 user: mistachkin
Context
2014-07-18
22:04
Add initial performance tests for the SQLiteDataReader class. check-in: d3be3b1abe user: mistachkin tags: trunk
2014-07-02
17:45
Update a statement in the provider limitations documentation regarding deferred transaction locking semantics. Fix for [425f060dec]. check-in: 45cc5a21fa user: mistachkin tags: trunk
2014-06-23
22:55
Final updates for the 1.0.93.0 release. check-in: 47ba62f72c user: mistachkin tags: trunk, release, release-1.0.93.0
Changes
Hide Diffs Unified Diffs Show Whitespace Changes Patch

Changes to Doc/Extra/Provider/limitations.html.

55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
        Hierarchical DataReaders are not supported. In the 
        case of transactions, any SQLiteCommand created on a connection will (when 
        executed) automatically join a transaction in progress, regardless of whether 
        that transaction was created before or after the command.</p>
      <p>A SQLiteCommand object <b>can</b> be re-assigned a new SQLiteConnection object 
        as long as no DataReaders are active on the command.</p>
      <p>Opening a transaction is considered a write operation, so only use them when 
        you want to write to the database! If you hold open a transaction, all readers on other
        connections
        will be blocked until the transaction is closed!</p>
      <p></p>
      <h4 class="subHeading">Thread Safety</h4>
      <p>Multi-threading in SQLite must be done carefully. Here are the restrictions:</p>
      <ul>
        <li>
          <b>You May</b>
        Clone() a SQLiteConnection object in one thread and pass the cloned object to 







|
|
|







55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
        Hierarchical DataReaders are not supported. In the
        case of transactions, any SQLiteCommand created on a connection will (when
        executed) automatically join a transaction in progress, regardless of whether
        that transaction was created before or after the command.</p>
      <p>A SQLiteCommand object <b>can</b> be re-assigned a new SQLiteConnection object
        as long as no DataReaders are active on the command.</p>
      <p>Opening a transaction is considered a write operation, so only use them when
        you want to write to the database! If you hold open an &quot;immediate&quot;
        transaction, all readers on other connections will be blocked until the
        transaction is closed!</p>
      <p></p>
      <h4 class="subHeading">Thread Safety</h4>
      <p>Multi-threading in SQLite must be done carefully. Here are the restrictions:</p>
      <ul>
        <li>
          <b>You May</b>
        Clone() a SQLiteConnection object in one thread and pass the cloned object to