Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | no message |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | sourceforge |
Files: | files | file ages | folders |
SHA1: |
a56e1d7f7c4d6aa302144e4fc3eb5fde |
User & Date: | rmsimpson 2006-02-09 23:24:38.000 |
Context
2006-02-10
| ||
04:47 | no message check-in: b83a6acadd user: rmsimpson tags: sourceforge | |
2006-02-09
| ||
23:24 | no message check-in: a56e1d7f7c user: rmsimpson tags: sourceforge | |
23:24 | Implement IsLong schema column check-in: 84578f9c4f user: rmsimpson tags: sourceforge | |
Changes
Added Doc/Extra/dbfactorysupport.html.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title>DBProviderFactories Support</title> <meta name="GENERATOR" content="Microsoft Visual Studio .NET 7.1"> <meta name="vs_targetSchema" content="http://schemas.microsoft.com/intellisense/ie5"> <link rel="stylesheet" type="text/css" href="MSDN.css"> </head> <body id="bodyID" class="dtBODY"> <div id="nsbanner"> <div id="bannerrow1"> <table class="bannerparthead" cellspacing="0" ID="Table1"> <tr id="hdr"> <td class="runninghead">DbProviderFactories Support</td> <td class="product"> </td> </tr> </table> </div> <div id="TitleRow"> <h1 class="dtH1">SQLite.NET Class Library Documentation</h1> </div> </div> <div id="nstext"> <h1 class="dtH1">DbProviderFactories and You</h1> <p>One of the great new features of ADO.NET 2.0 is the use of reflection as a means of instantiating database providers programmatically. The information .NET uses to enumerate the available data providers in the system is relatively simple. It merely looks in the machine.config and in your own app.config file for some XML data to tell it what providers are installed and what assemblies those providers are in. </p> <h4> Scenario 1: Version Independent (does not use the Global Assembly Cache)</h4> <p> This method allows you to drop any new version of the System.Data.SQLite.DLL into your application's folder and use it without any code modifications or recompiling. Add the following code to your app.config file:</p> <div class="syntax"> <PRE><configuration> <system.data> <DbProviderFactories> <remove invariant="System.Data.SQLite"/> <add name="SQLite Data Provider" invariant="System.Data.SQLite" description=".Net Framework Data Provider for SQLite"<br /> type="System.Data.SQLite.SQLiteFactory, System.Data.SQLite" /> </DbProviderFactories> </system.data> </configuration> </PRE> </div> <h4> Scenario 2: Version Dependent, using either the DLL located in the same folder as the application or the Global Assembly Cache</h4> <p> This method expands on the above XML to provide the version number and key token of the SQLite DLL so it can be found either in the same folder as the application or looked up in the GAC. The downside to this method is that DbProviderFactories will use this version information to only load the version specified. This means if you update the DLL, you must also update this XML.</p> <div class="syntax"> <PRE> <configuration> <system.data> <DbProviderFactories> <remove invariant="System.Data.SQLite"/> <add name="SQLite Data Provider" invariant="System.Data.SQLite" description=".Net Framework Data Provider for SQLite" type="System.Data.SQLite.SQLiteFactory, System.Data.SQLite, Version=1.0.25.0, Culture=neutral, PublicKeyToken=db937bc2d44ff139"/> </DbProviderFactories> </system.data> </configuration> </pre> </div> <p> The following C# code demonstrates instantiating SQLite through DbProviderFactories:</p> <div class="syntax"><pre> DbProviderFactory fact = DbProviderFactories.GetFactory("System.Data.SQLite"); using (DbConnection cnn = fact.CreateConnection()) { cnn.ConnectionString = "Data Source=test.db3"; cnn.Open(); }</pre> </div> <hr> <div id="footer"> <p> <a href="mailto:robert@blackcastlesoft.com?subject=SQLite.NET%20Class%20Library%20Documentation%20Feedback:%20Factory%20Support"> Send comments on this topic.</a> </p> <p> </p> </div> </div> </body> </html> |
Added Doc/Extra/designer.html.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title>Design-Time Support</title> <meta name="GENERATOR" content="Microsoft Visual Studio .NET 7.1"> <meta name="vs_targetSchema" content="http://schemas.microsoft.com/intellisense/ie5"> <link rel="stylesheet" type="text/css" href="MSDN.css"> </head> <body id="bodyID" class="dtBODY"> <div id="nsbanner"> <div id="bannerrow1"> <table class="bannerparthead" cellspacing="0" ID="Table1"> <tr id="hdr"> <td class="runninghead"> Design-Time Support</td> <td class="product"> </td> </tr> </table> </div> <div id="TitleRow"> <h1 class="dtH1">SQLite.NET Class Library Documentation</h1> </div> </div> <div id="nstext"> <h1 class="dtH1">Installing SQLite Visual Studio Design-Time Support</h1> <p>Supporting the Visual Studio query designer and allowing you to manipulate SQLite databases from within Visual Studio is a great time-saver. Though the support is not yet fully-implemented, there's certainly enough there to keep you busy. You can create databases, design and execute queries, create typed datasets and lots more all from Visual Studio.</p> <h3> Installation Instructions</h3> <p> In Windows Explorer, navigate to <STRONG>SQLite.Net\bin\Designer</STRONG> and execute the <STRONG>INSTALL.EXE</STRONG> program. It will automatically detect what eligible Visual Studio products are installed, and allow you to check and uncheck which environments to install the designer for.</p> <h3> Express Edition Limitations</h3> <p>All Express Editions (except Visual Web Developer) are hard-coded to only allow you to design for Jet and Sql Server Database Files. The only way for SQLite to install its designer is to temporarily replace one of the existing "approved" designers. Therefore, when you install the SQLite designer for one of these express editions, it will temporarily replace the Microsoft Access designer. You can revert back to the Access designer simply by re-running the install.exe program and un-checking the boxes.</p> <hr> <div id="footer"> <p> <a href="mailto:robert@blackcastlesoft.com?subject=SQLite.NET%20Class%20Library%20Documentation%20Feedback:%20Designer%20Support"> Send comments on this topic.</a> </p> <p> </p> </div> </div> </body> </html> |
Added Doc/Extra/limitations.html.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title>Getting Started</title> <meta name="GENERATOR" content="Microsoft Visual Studio .NET 7.1"> <meta name="vs_targetSchema" content="http://schemas.microsoft.com/intellisense/ie5"> <link rel="stylesheet" type="text/css" href="MSDN.css"> </head> <body id="bodyID" class="dtBODY"> <div id="nsbanner"> <div id="bannerrow1"> <table class="bannerparthead" cellspacing="0" ID="Table1"> <tr id="hdr"> <td class="runninghead">Provider Limitations</td> <td class="product"> </td> </tr> </table> </div> <div id="TitleRow"> <h1 class="dtH1">SQLite.NET Class Library Documentation</h1> </div> </div> <div id="nstext"> <h1 class="dtH1">Limitations of this ADO.NET SQLite Data Provider</h1> <p>As providers go, this one doesn't have many restrictions. SQLite has no support for row-level or table-level locks. Therefore when a DataReader is active the database cannot be written to, and when the database is open for writing no DataReaders can be open. The SQLite.NET provider attempts to retry internally if a database is locked, up to the CommandTimeout property of the command in question.</p> <p>SQLite is inherently type-less, and only understands a few basic datatypes natively. They are (in .NET-speak) Int64, Double, String and Blob. The SQLite.NET provider will use the database schema information it can glean to enforce type-ness, but it is an inexact science.</p> <p>Nested transactions and 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 will be blocked until the transaction is closed!</p> <p></p> <h4 class="dtH4">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 another thread. Once passed, the other thread becomes the new owner of the cloned connection, and the original thread must not keep a reference to the clone or call any methods on the clone. <LI> <STRONG>You May</STRONG> create multiple threads, and those threads can create their own SQLiteConnection and subsequent objects for accessing a database. Multiple connections on multiple threads to the same database file are perfectly acceptable and will behave predictably. <li> <b>You May NOT</b> call methods or properties or otherwise reference any SQLite provider classes that belong to another thread. <li> <b>You May NOT</b> pass a SQLiteCommand, SQLiteDataReader, SQLiteDataAdapter or any other SQLite provider class except a cloned SQLiteConnection to another thread.</li> </ul> <p>Understand again that SQLite has no fine-grained locking mechanisms. It is therefore your own responsibility in a multi-threaded environment to handle potential timeouts that may occur if a long-running query in one thread prevents a query in another thread from executing. These timeouts will only occur if one thread is attempting to read while another thread is attempting to write. Whichever thread got its lock first will be the one to execute, and the other thread will block until the CommandTimeout value elapses or the other thread finishes.</p> <hr> <div id="footer"> <p> <a href="mailto:robert@blackcastlesoft.com?subject=SQLite.NET%20Class%20Library%20Documentation%20Feedback:%20Limitations"> Send comments on this topic.</a> </p> <p> </p> </div> </div> </body> </html> |
Added Doc/Extra/optimizing.html.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title>Optimizing SQLite</title> <meta name="GENERATOR" content="Microsoft Visual Studio .NET 7.1"> <meta name="vs_targetSchema" content="http://schemas.microsoft.com/intellisense/ie5"> <link rel="stylesheet" type="text/css" href="MSDN.css" /> </head> <body id="bodyID" class="dtBODY"> <div id="nsbanner"> <div id="bannerrow1"> <table class="bannerparthead" cellspacing="0" ID="Table1"> <tr id="hdr"> <td class="runninghead">Optimizing for SQLite</td> <td class="product"> </td> </tr> </table> </div> <div id="TitleRow"> <h1 class="dtH1">SQLite.NET Class Library Documentation</h1> </div> </div> <div id="nstext"> <h1 class="dtH1">Tips on Optimizing Your Queries</h1> <p>The next few paragraphs will attempt to give you a few rudimentary rules for speeding up your queries in general, and especially how SQLite is adversely affected by the kinds of SQL behaviors you may have taken for granted in other providers. It is by no means a complete optimization guide. For even more details on optimizing your queries, visit <a href="http://www.sqlite.org">sqlite.org</a>.</p> <h4 class="dtH4">The Importance of Transactions</h4> <p>If you are inserting data in SQLite without first starting a transaction: <b>DO NOT PASS GO! Call BeginTransaction() right now, and finish with Commit()!</b> If you think I'm kidding, think again. SQLite's A.C.I.D. design means that every single time you insert any data outside a transaction, an implicit transaction is constructed, the insert made, and the transaction destructed. <b>EVERY TIME.</b> If you're wondering why in the world your inserts are taking 100x longer than you think they should, look no further.</p> <h4 class="dtH4">Prepared Statements</h4> <p>Lets have a quick look at the following code and evaluate its performance:</p> <div class="syntax"> <pre> using (SQLiteCommand mycommand = new SQLiteCommand(myconnection)) { int n; for (n = 0; n < 100000; n ++) { mycommand.CommandText = String.Format("INSERT INTO [MyTable] ([MyId]) VALUES({0})", n + 1); mycommand.ExecuteNonQuery(); } }</pre> </div> <p>This code seems pretty tight, but if you think it performs well, you're dead wrong. Here's what's wrong with it:</p> <ul> <li> I didn't start a transaction first! This insert is dog slow!</li> <li> The CLR is calling "new" implicitly 100,000 times because I am formatting a string in the loop for every insert</li> <li> Since SQLite precompiles SQL statements, the engine is constructing and deconstructing 100,000 SQL statements and allocating/deallocating their memory</li> <li> All this construction and destruction is involving about 300,000 more native to managed interop calls than an optimized insert</li> </ul> <p>So lets rewrite that code slightly:</p> <div class="syntax"> <pre> using (SQLiteTransaction mytransaction = myconnection.BeginTransaction()) { using (SQLiteCommand mycommand = new SQLiteCommand(myconnection)) { SQLiteParameter myparam = new SQLiteParameter(); int n; mycommand.CommandText = "INSERT INTO [MyTable] ([MyId]) VALUES(?)"; mycommand.Parameters.Add(myparam); for (n = 0; n < 100000; n ++) { myparam.Value = n + 1; mycommand.ExecuteNonQuery(); } } mytransaction.Commit(); } </pre> </div> <p>Now this is a blazing fast insert for <b><i>any</i></b> database engine, not just SQLite. The SQL statement is prepared one time -- on the first call to ExecuteNonQuery(). Once prepared, it never needs re-evaluating. Furthermore, we're allocating no memory in the loop and doing a very minimal number of interop transitions. Surround the entire thing with a transaction, and the performance of this insert is so far and away faster than the original that it merits a hands-on-the-hips pirate-like laugh.</p> <p>Every database engine worth its salt utilizes prepared statements. If you're not coding for this, you're not writing optimized SQL, and that's the bottom line. </p> <hr /> <div id="footer"> <p> <a href="mailto:robert@blackcastlesoft.com?subject=SQLite.NET%20Class%20Library%20Documentation%20Feedback:%20Optimizing"> Send comments on this topic.</a> </p> <p> </p> </div> </div> </body> </html> |
Added Doc/Extra/version.html.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title>Version History</title> <meta name="GENERATOR" content="Microsoft Visual Studio .NET 7.1"> <meta name="vs_targetSchema" content="http://schemas.microsoft.com/intellisense/ie5"> <link rel="stylesheet" type="text/css" href="MSDN.css"> </head> <body id="bodyID" class="dtBODY"> <div id="nsbanner"> <div id="bannerrow1"> <table class="bannerparthead" cellspacing="0" ID="Table1"> <tr id="hdr"> <td class="runninghead">Provider History</td> <td class="product"> </td> </tr> </table> </div> <div id="TitleRow"> <h1 class="dtH1">SQLite.NET Class Library Documentation</h1> </div> </div> <div id="nstext"> <h1 class="dtH1">Version History</h1> <p><b>1.0.26.0 - February 10, 2006</b></p> <ul> <li>Code merge with SQLite 3.3.4</li><li>Fixed an encryption bug when changing the password of databases over 1gb in size. </li><li>Fixed various designer issues related to construction of named parameters. </li><li>Implemented the SourceColumnNullMapping property of SQLiteParameter to fix a DbCommandBuilder code generation bug. </li><li>Removed the runtime dependency on MSVCR80.DLL. File size is somewhat larger for the varying desktop versions, but the Compact Framework version remains the same.</li><li>Created an install program to manage installation and uninstallation of the SQLite design-time support.</li> <li>Designer support now works for all Visual Studio editions, including all Express Editions.</li> <li>Design-time installer will now remove (if present) the machine.config SQLite entries in favor of installing the xml code into the devenv.exe.config file (or any of the variations for express editions). The officially-accepted behavior of using DbProviderFactories is to add the code to your app.config file, and the machine.config file should not be touched.</li> </ul> <p><b>1.0.25.0 - January 31, 2006</b></p> <ul> <li>Code merge with SQLite 3.3.3</li><li>Added automatic distributed transaction enlistment and implemented the DbConnection.EnlistTransaction method for manual enlistment.</li> <li>Nested transactions are now supported.</li> <li>Rearranged the timing of SetPassword(), which now must be called before the database is opened instead of afterwards. Optionally, the password can be supplied in the ConnectionString.</li> <li>Fixed a bug in SQLiteFunction that caused a failure when an empty resultset was returned and a custom user aggregate function was used in the query.</li> <li>The designer has had another round of cleanup applied, in preparation for moving to a VS package.</li> <li>Added SQLiteMetaDataCollectionNames class.</li> </ul> <p><b>1.0.24.6 beta - January 23, 2006</b></p> <ul> <li>This beta is built from sqlite.org's 3.3.2 beta.</li><li>Eliminated the static linking of mscoree from all binaries. Native projects can now use the library without any dependencies on the .NET framework, while managed projects continue to be able to use the library normally.</li></ul> <p><b>1.0.24.5 beta - January 20, 2006</b></p> <ul> <li>This beta is built from sqlite.org's 3.3.1 alpha and contains development-in-progress code. Therefore no guarantees can be made regarding its suitability for production use.</li> <li><strong>You no longer need to distribute 2 files on the CompactFramework. You can delete SQLite.Interop.DLL entirely. </strong>I wrote a custom tool called "mergebin" (available in the source zip file) which combines the two libraries and gets around a glaring defect in the VS2005 linker for ARM processors which doesn't allow you to link netmodules.</li> <li><strong>x64 and ia64 builds now use the same strong name as the x86 build.</strong> This means breaking backward compatibility, but it was necessary in order to allow you to drop any of those 3 builds onto a PC and have your .NET program run properly. Prior to this, you'd get an error if you built your program using the x86 build, and then installed the x64 version on a target machine and tried to run your program against it.</li> <li>The entire source project has been gone over top to bottom. A debug build no longer combines the binaries into a single module, which was preventing proper debugging.</li></ul> <p><b>1.0.24.4 beta - January 16, 2006</b></p> <ul> <li>This beta is built from sqlite.org's 3.3.1 alpha and contains development-in-progress code. Therefore no guarantees can be made regarding its suitability for production use.</li> <li>Fixed a bug in the UTF-16 handling code for preparing statements due to a behavioral change in SQLite 3.3.0.</li> <li>Added pager.c code necessary to cleanup after an encrypted file is closed.</li> <li>Fixed an encryption bug that caused a fault when an encrypted file was rolled back.</li> <li>Modified the testcase code to take advantage of optimizations regarding the use of a DbCommandBuilder. DataAdapter insert speed increased dramatically as a result.</li> </ul> <p><b>1.0.24.3 beta - January 10, 2006</b></p> <ul> <li>This beta is built from sqlite.org's CVS HEAD (as it appeared at of the date of this beta) and contains development-in-progress code. Therefore no guarantees can be made regarding its suitability for production use.</li><li>Added support for database encryption at the pager level. Databases are encrypted using a 128-bit RC4 stream algorithm. To open an existing encrypted database, you may now specify a "Password={password}" text in the ConnectionString, or you may call the SQLiteConnection.SetPassword() function to set the password on an open connection. To encrypt existing non-encrypted databases or to change the password on an encrypted database, you must use the SQLiteConnection.ChangePassword() function. If you use SetPassword() instead of specifying a password in the connection string, or call ChangePassword() you may use a binary byte array or a text string as the password.</li> <li>Rewrote the locking implementation for the Compact Framework. It is now more robust and incorporates into the SQLite codebase more efficiently than the previous CE adaptation.</li> <li>Moved some of the embedded schema XML data into a resource file to ease code readability.</li> <li>Automated the fixup of the original sqlite codebase's source prior to compiling, to ease merging with sqlite.org's source. </li> </ul> <p><b>1.0.24.2 - December 30, 2005</b></p> <ul> <li>Fixed the SQLiteDataReader.HasRows property to return the proper value.</li> <li>Implemented the inadvertently neglected RecordsAffected property on SQLiteDataReader. </li> <li>SQLiteFunction static constructor was changed to pre-filter classes with only the SQLiteFunctionAttribute. The code was throwing an exception when certain assemblies were referenced in a project. </li> <li>Fixed the SQLiteDataAdapter OnRowUpdated event, which was using the wrong variable to find the attached event handler and subsequently not raising the event.</li> <li>Small optimizations and fixes to SQLiteDataReader.NextResult(). </li> </ul> <p><b>1.0.24.1 - December 19, 2005</b></p> <ul> <li>Update core SQLite engine to 3.2.8 </li></ul> <p><b>1.0.24 - December 9, 2005</b></p> <ul> <li>Fixed the<em> Catalogs</em> schema bug that caused attached databases not to be re-attached to a cloned connection </li> <li>Enhanced transactions to allow for a deferred or immediate writelock. SQLiteConnection.BeginTransaction() now has an additional overload to support it </li> <li>Commands are now prepared as they are executed instead of beforehand. This fixes a bug whereby a multi-statement command that alters the database and subsequently references the altered data would fail during Prepare().</li><li>Tightened up the SQLiteDataReader to prevent reading columns before calling the first Read() and to prevent reading columns after the last Read().</li> <li>A more descriptive error is thrown if there aren't enough parameters in the command to satisfy the parameters required by the statement(s). </li> </ul> <p><b>1.0.23 - November 21, 2005</b></p> <ul> <li>Named parameters may now begin with <strong>@</strong> to ease portability of the provider. SQLite's named parameters are ordinarily prefixed with a <strong>: </strong> or<strong> $</strong>. The designer will still use the <strong>$</strong> prefix however, since its more compatible with the default SQLite engine.</li><li>Added several alternate ISO8601 date/time formats to SQLiteConvert.cs to increase compatibility.</li> <li>Relaxed coersion restrictions to work better with SQLite's inherent typelessenss. </li> </ul> <p><b>1.0.22 - November 11, 2005</b></p> <UL> <li>Fixed some globalization issues which resulted in incorrect case-insensitive comparisons</li> <li>Fixed a bug in the routine that finds all user-defined functions in a loaded assembly. It would throw an exception if any of the types in the assembly could not be loaded. The exception is now caught and handled appropriately.</li> </UL> <p><b>1.0.21 - November 4, 2005</b></p> <UL> <li>Fixed a designer bug when creating typed datasets with parameterized queries. </li><li>The above fix then exposed another bug in the datareader's ability to query schema information on parameterized commands, which was also fixed. </li> <li>Compiled against the RTM version of VS2005. </li> <li>Rewrote the design-time install script to use the XML DOM objects when writing to the machine.config and to automatically register the DLL in the GAC.</li> <LI>Made changes to the app.config descriptions and help file to improve version-independent factory support. </li> </UL> <P><STRONG>1.0.20 - October 19, 2005</STRONG></P> <UL> <LI> Fixed a shortcut in SQLiteBase.GetValue which was insufficient for international environments. The shortcut was removed and the "proper" procedure put in. </UL> <P><STRONG>1.0.19 - October 5, 2005</STRONG></P> <UL> <LI> Code merge with SQLite 3.2.7 <LI> Fixed bugs in the CE port code (os_wince.c) which were brought to light by recent changes in the SQLite engine. <LI> Recompiled and modified to be compatible with the September VS2005 Release Candidate.<BR> Beta 2 users should continue to use 1.0.18.1</LI></UL> <P><STRONG>1.0.18.1 - September 19, 2005</STRONG></P> <UL> <LI> Code merge with SQLite 3.2.6</LI></UL> <P><STRONG>1.0.18 - September 1, 2005</STRONG></P> <UL> <li> Added type-specific method calls when using the various SQLite classes that would've normally returned a a generic Db base class, which aligns the code better with the Microsoft-supplied data providers.</li></UL> <p><b>1.0.17 - August 26, 2005</b></p> <ul> <li> Code merge with SQLite 3.2.5 <li> Added Itanium and x64 build settings to the project (needs testing) <li> Bugfixes and enhancements to several schema types <li> Additional design-time support to include index and foreign key enumerations. Requires re-registering the designer using INSTALL.CMD. The new designer code now allows the VS query designer and typed datasets to automatically link up foreign keys, use indexes, and automatically generate relationships from the schema.<li> Additional static methods on SQLiteConnection to create a database file, encrypt a file using the Encrypted File System (EFS) on NTFS (requires NT 2K or above) and NTFS file compression</li> </ul> <p><b>1.0.16 - August 24, 2005</b></p> <ul> <li> Code merge with SQLite 3.2.4 with the large delete bugfix in CVS (which will become 3.2.5 soon) <li> Added new GetSchema() types: IndexColumns, ViewColumns, ForeignKeys</li> </ul> <p><b>1.0.15 - August 22, 2005</b><br> </p> <ul> <li> Code merge with SQLite 3.2.3 <LI> Minor updates for better design-time experience. More design-time code to follow in subsequent releases.</LI> </ul> <p><b>1.0.14 - August 16, 2005</b><br> </p> <ul> <li> Fixed a bug in the SQLiteDataAdapter due to insufficient implementation of the class. The RowUpdating and RowUpdated events are now properly implemented, but unfortunately inserting and updating data in a DataTable or DataSet is now much slower. This is the proper design however, so the changes are here to stay. <LI> Lots of schema changes to support Visual Studio's Data Designer architecture.<li>Added Designer support for the provider. It's not 100%, but you can design queries, add typed datasets and perform quite a number of tasks all within Visual Studio now.</li></ul> <P><B>1.0.13 - August 8, 2005</B><BR> </P> <DIV> <UL> <LI> Fixed a named parameter bug in the base SQLite_UTF16 class, which of course only showed up when a database connection was opened using the UseUTF16Encoding=True parameter. <LI> Fixed a performance issue in SQLite_UTF16 involving string marshaling.</LI></UL> </DIV> <P><B>1.0.12 - August 5, 2005</B><BR> </P> <DIV> <UL> <LI> Full support for the Compact Framework. Each build (Debug/Release) now has a platform, either Win32 or Compact Framework. The correct projects are built accordingly. See the <A href="#redist">Distributing SQLite</A> section for information on what files need to be distributed for each platform. <LI> Modified SQLite3.Reset() and Step() functions to transparently handle timeouts while waiting on the database to become available (typically when a writer is waiting on a reader to finish, or a reader is waiting on a writer to finish). <LI> Lots of code cleanup as suggested by the Code Analyzer (FxCop). <LI> Lots of updates to the helpfile (as you can see). <LI> Statements were already prepared lazily in a SQLiteCommand, but now its even more lazy. Statements are now only prepared if the statements haven't been previously prepared and a Prepare() function is called (and the command is associated with a connection) or just prior to the command being executed. </LI></UL> </DIV> <P><B>1.0.11 - August 1, 2005</B><BR> </P> <UL> <LI> <STRONG>For everything except the Compact Framework, System.Data.SQLite.DLL is now the <EM>only</EM> DLL required to use this provider!</STRONG> The assembly is now a multi-module assembly, containing both the native SQLite3 codebase and the C# classes built on top of it. The Compact Framework version (when completed) will not be able to support this feature, so backwards compatibility with the Compact Framework has been preserved for the future. <LI> Fixed a bug in SQLiteCommand.ExecuteScalar() that caused it to stop executing commands once it obtained the first column of the first row-returning resultset. Any remaining statements after the row-returning statement was ignored. </LI> </UL> <P><B>1.0.10 - June 10, 2005</B><BR> </P> <UL> <LI> Fixed a bug in the SQLite3.cs Prepare() function that created a statement even when the SQLite engine returned a NULL pointer. Typically this occurs when multiple statements are processed and there are trailing comments at the end of the statement. <LI> Fixed a bug in SQLiteStatement.cs that retrieved parameter names for a parameterized query. SQLite's parameters are 1-based, and the function was starting at 0. This was fine when all parameters were unnamed, but for named parameters it caused the parameters to be out of whack. </LI> </UL> <P><B>1.0.09a - May 25, 2005</B><BR> </P> <UL> <LI> Fixed a broken helpfile and corrected some obsolete help remarks in SQLiteFunction.cs <LI> Added a version resource to the SQLite.Interop.DLL. </LI></UL> <P><B>1.0.09 - May 24, 2005</B><BR> </P> <UL> <LI> Code merge with the latest 3.21 version of SQLite. <LI> Removed obsolete methods and properties for Whidbey Beta 2</LI></UL> <P><B>1.0.08 Refresh - Mar 24, 2005<BR> </B> </P> <UL> <LI> Code merge with the latest 3.20 version of SQLite. <LI> Recompiled the help file to fix a build error in it. </LI> </UL> <P><B>1.0.08 - Mar 11, 2005<BR> </B> </P> <UL> <LI> Added additional #if statements to support the old beta 1 edition of VS2005. <LI> Code merged the SQLite 3.14 source. </LI> </UL> <P><B>1.0.07 - Mar 5, 2005</B><BR> </P> <UL> <LI> Made more optimizations to frequently-called functions, resulting in significant performance gains in all tests. <LI> Recompiled the binaries using the latest VS2005 February CTP, resulting in yet more significant speed gains. The 100k insert test used to take 3.5 seconds and the insertwithidentity took almost 8 seconds. With the above two changes, those tests are now executing in 1.9 and 4.9 seconds respectively.</LI></UL> <P><B>1.0.06 - Mar 1, 2005<BR> </B> </P> <UL> <LI> Speed-ups to SQLiteDataReader. It was interop'ing unnecessarily every time it tried to fetch a field due to a logic error. <LI> Changed/Added some code to SQLiteConvert's internal DbType, Type and TypeAffinity functions. <LI> Fixed the SQLiteDataReader to obey the flags set in the optional CommandBehavior flag from SQLiteCommand.ExecuteReader(). <LI> Changed the default page size to 1024 to reflect the defaults of SQLite. Ignores the "Page Size" connection string option for memory databases, as tests revealed that changing it resulted in memory corruption errors. <LI> Performance enhancements to the SQLiteCommand and SQLiteStatement classes which reduced the 100,000 row insert execution time as well as the various Function execution times significantly. </LI> </UL> <P><B>1.0.05 - Feb 25, 2005</B> </P> <UL> <LI> Fixed the SQLite3 C# class step/reset functions to accomodate schema changes that invalidate a prepared statement. Statements are recompiled transparently. <LI> Moved all native DLL declarations to an UnsafeNativeMethods class. <LI> Split several classes into their own modules for readability. <LI> Renamed many internal variables, reviewed access to variables marked as internal and altered their protection levels accordingly. <LI> Due to the presence of the altered sqlite3 codebase and so many added interop functions, I decided to rename the sqlite3 C project and the DLL to SQLite.Interop.DLL. This is the same core sqlite3 codebase but designed specifically for this ADO.NET provider. This eliminates any possibility of someone dropping another build of sqlite3.dll into the system and rendering the provider inoperable. In the future if the folks at sqlite.org finally introduce a method of retrieving column usage for an arbitrary prepared statement, I'll retool this library to be a lightweight function call wrapper around the core binary distribution. <LI> Added [SuppressUnmanagedCodeSecurity] attribute to the UnsafeNativeMethods class which brings VS2005 November CTP execution speeds inline with the December CTP. <LI> Added a <B>bin</B> directory to the project root where pre-compiled binaries can be found. <LI> Added a <B>doc</B> directory where preliminary documentation on the class library can be found. <LI> Documented a lot more of the classes internally. </LI> </UL> <P><B>1.0.04 - Feb 24, 2005</B> </P> <UL> <LI> Removed the SQLiteContext class and revamped the way UserFunctions work to simplify the imlementation. <LI> Fixed a counting bug in the TestCases class, specifically in the function tests where I wasn't resetting the counter and it was consequently reporting intrinsic and raw select calls as being much much faster than they actually were. The numbers are now much closer to what I expected for performance, with .NET user-functions still being the slowest, but only by a small margin. <LI> Small performance tweaks to SQLiteDataReader. <LI> Added PageSize to the SQLiteConnectionStringBuilder and subsequently to the SQLiteConnection <LI> Added a PRAGMA encoding=XXX execution statement to the SQLiteConnection after opening a connection. </LI> </UL> <P><B>1.0.03 - Feb 23, 2005</B> </P> <UL> <LI> Fixed up SQLiteCommandBuilder to correct implementation errors, which resulted in an enormous performance boost in the InsertMany test. 10,000 row insert that executed in 1500ms now executes in 500ms. <LI> Fixed several errors in the SQLite3_UTF16 class. ToString() was working incorrectly and the Open() method failed to register user defined functions and collations. <LI> Fixed a bug in SQLiteCommand.ClearCommands() whereby only the first statement was being properly cleaned up. <LI> Fixed a bug in SQLiteDataReader whereby calling NextResult() would not properly reset the previously-executed command in the sequence. <LI> Added an InsertManyWithIdentityFetch test, which appends a select clause to populate the ID of the last inserted row into the InsertCommand, demonstrating ADO.NET's ability to auto-fetch identity columns on insert. </LI> </UL> <P><B>1.0.02 - Feb 21, 2005</B></P> <UL> <LI> Tweaks to the xxx_interop functions that return char *'s, so they also return the length. Saves an interop call to get the UTF-8 string length during conversion to a .NET string. <LI> Reworked the whole interop.c thing into interop.h and reduced the code required to merge the main sqlite3 codebase. <LI> Added support for user-defined collations. </LI> </UL> <hr> <div id="footer"> <p> <a href="mailto:robert@blackcastlesoft.com?subject=SQLite.NET%20Class%20Library%20Documentation%20Feedback:%20Version%20History"> Send comments on this topic.</a> </p> <p> </p> </div> </div> </body> </html> |
Added Doc/Extra/welcome.html.
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title>Introduction</title> <meta name="GENERATOR" content="Microsoft Visual Studio .NET 7.1"> <meta name="vs_targetSchema" content="http://schemas.microsoft.com/intellisense/ie5"> <link rel="stylesheet" type="text/css" href="MSDN.css"> </head> <body id="bodyID" class="dtBODY"> <div id="nsbanner"> <div id="bannerrow1"> <table class="bannerparthead" cellspacing="0" ID="Table1"> <tr id="hdr"> <td class="runninghead">SQLite.NET Class Library</td> <td class="product"> </td> </tr> </table> </div> <div id="TitleRow"> <h1 class="dtH1">SQLite.NET Class Library Documentation</h1> </div> </div> <h1 class="dtH1">About SQLite.NET</h1> <p>This class library is an ADO.NET 2.0 wrapper around the popular (and free!) SQLite database engine. For information on SQL syntax, features of SQLite and a good understanding of how it works and what it does, I highly recommend heading over to <a target="_blank" href="http://www.sqlite.org">sqlite.org</a> and reading the documentation there.</p> <P>The C# provider, the very minor C code modifications to SQLite, documentation and etc were written by <A href="mailto:robert@blackcastlesoft.com">Robert Simpson</A>, and the SourceForge project page can be found <A target="_blank" href="http://sourceforge.net/projects/sqlite-dotnet2"> here</A>.</P> <DIV> <br> </DIV> <h1 class="dtH1">What's New?</h1> <p><a href="version.html">Click here to see the version history of this SQLite.NET provider</a></p> <DIV> <br> </DIV> <h1 class="dtH1">What's Coming Up?</h1> <p>There's a few things I'm aiming to do in the near future: </p> <DIV> <ul> <LI> More class documentation and examples. I'll also be integrating a lot of the documentation from the official <A target="_blank" href="http://www.sqlite.org"> sqlite.org</A> website into the helpfile for quick and easy access.</LI> <li>Design-time support for DDL, enabling you to create/alter tables, manage indexes and foreign keys, etc.</li> </ul> </DIV><div> <br> </div> <h1 class="dtH1">Using this library</h1> <p>The following are links to information on various aspects of the library and how to use it in your application(s) </p> <p><a href="designer.html">How to install Visual Studio Design-Time Support</a></p> <P><A href="dbfactorysupport.html">How to configure and enumerate SQLite.NET through the DbProviderFactories object</A></P> <p><a href="optimizing.html">Getting the best performance out of SQLite</a></p> <p><a href="limitations.html">Limitations of the SQLite.NET provider and the SQLite engine (compared to other providers and engines)</a></p><div> <br> </div> <h1 class="dtH1">SQLite.NET Provider Features</h1> <p>This SQLite provider implements every feature of the underlying SQLite database engine without omission. Here's a brief summary:</p><div> <UL> <LI> Written from scratch on VS2005 specifically for ADO.NET 2.0, implenting all the base classes and features recently introduced in the framework, including automatic transaction enlistment.<li>Supports the Full and Compact .NET Framework, as well as native C/C++ development. 100% binary compatible with the original sqlite3.dll. </li> <li> On the Compact Framework, it is faster than the newly-introduced Sql Server Mobile. SQLite's installed size is a fraction of Sql Mobile's. It uses less memory at runtime, runs queries faster, and has a smaller database file size as well. </li> <li>Encrypted database support. Encrypted databases are fully encrypted and support both binary and cleartext password types. </li> <li>Visual Studio 2005 Design-Time Support. You can add a SQLite database to the Servers list, design queries with the Query Designer, drag-and-drop tables onto a Typed DataSet, etc. </li> <li> Single file redistributable. The core sqlite3 codebase and the ADO.NET wrapper are combined into one multi-module assembly. </li> <li>Binaries included for Itanium, x64, x86 and ARM processors. </li> <li> DbProviderFactory support. </li> <li> Full support for ATTACH'ed databases. Exposed as <i>Catalogs</i> in the schema. When cloning a connection, all attached databases are automatically re-attached to the new connection. </li> <li> DbConnection.GetSchema(...) support includes the <i>MetaDataCollections</i>, <i> DataSourceInformation</i>, <i>Columns</i>, <i>Tables</i>, <i>Views, ViewColumns, </i> <i>Catalogs, </i><i>Indexes, IndexColumns </i>and <em>ForeignKeys</em> keywords. </li> <li> Enhanced DbDataReader.GetSchemaTable() functionality returns catalog, namespace and detailed schema information even for complex queries. </li> <li> Named and unnamed parameters. </li> <li> Full UTF-8 and UTF-16 support, each with optimized pipelines into the native database core. </li> <li> Multiple simultaneous DataReaders (one DataReader per Command however). </li> <li> Full support for user-defined scalar and aggregate functions, encapsulated into an easy-to-use base class in which only a couple of overrides are necessary to implement new SQL functions. </li> <li> Full support for user-defined collating sequences, every bit as simple to implement as user-defined functions and uses the same base class. </li> <li> Full source for the entire engine and wrapper. No copyrights. Public Domain. 100% free for commercial and non-commercial use. </li> </UL> </div> <br> <h1 class="dtH1">Distributing the Binaries</h1> <p><b>System.Data.SQLite.DLL</b> is a mixed assembly signed with a strong name in case you want to add it to the Global Assembly Cache (GAC). This is the only DLL required to be redistributed with your SQLite.NET application(s). It comes in 4 flavors: Win32, Itanium, X64 (AMD64) and ARM (Compact Framework). The Compact Framework library is signed with a separate strong name, but all the other versions share the same strong name so they can be interchanged where appropriate without any change to your application.</p> <hr> <div id="footer"> <p> <a href="mailto:robert@blackcastlesoft.com?subject=SQLite.NET%20Class%20Library%20Documentation%20Feedback:%20Welcome"> Send comments on this topic.</a> </p> <p> </p> </div> </body> </html> |
Changes to readme.htm.
1 2 3 4 5 6 7 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <title></title> </head> <body> ADO.NET 2.0 SQLite Data Provider<br> | | | | > < | | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <title></title> </head> <body> ADO.NET 2.0 SQLite Data Provider<br> Version 1.0.26.0 Feb 10, 2006<br> Using SQLite 3.3.4<br> Written by Robert Simpson (<a href="mailto:robert@blackcastlesoft.com">robert@blackcastlesoft.com</a>)<br> Released to the public domain, use at your own risk!<br> <br> The latest version can be downloaded <a href="http://sourceforge.net/projects/sqlite-dotnet2"> here</a> <br> <br> <b></b> <h2> <b>Features:</b><br> </h2> <UL> <LI> Written from scratch on VS2005 specifically for ADO.NET 2.0, implenting all the base classes and features recently introduced in the framework, including automatic transaction enlistment.<li>Supports the Full and Compact .NET Framework, as well as native C/C++ development. 100% binary compatible with the original sqlite3.dll.</li> <LI> On the Compact Framework, it is faster than the newly-introduced Sql Server Mobile. SQLite's installed size is a fraction of Sql Mobile's. It uses less memory at runtime, runs queries faster, and has a smaller database file size as well. <li>Encrypted database support. Encrypted databases are fully encrypted and support both binary and cleartext password types.</li> <LI> Visual Studio 2005 Design-Time Support. You can add a SQLite database to the Servers list, design queries with the Query Designer, drag-and-drop tables onto a Typed DataSet, etc. <LI> |
︙ | ︙ | |||
65 66 67 68 69 70 71 | an easy-to-use base class in which only a couple of overrides are necessary to implement new SQL functions. <LI> Full support for user-defined collating sequences, every bit as simple to implement as user-defined functions and uses the same base class. <LI> Full source for the entire engine and wrapper. No copyrights. | | < < < < | 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 | an easy-to-use base class in which only a couple of overrides are necessary to implement new SQL functions. <LI> Full support for user-defined collating sequences, every bit as simple to implement as user-defined functions and uses the same base class. <LI> Full source for the entire engine and wrapper. No copyrights. Public Domain. 100% free for commercial and non-commercial use. </LI></UL> <strong></strong> <h2> <strong>Design-Time Support (new as of 1.0.14)</strong></h2> <P>Until an installer is created, through a command-prompt or Windows Explorer, navigate to the <STRONG>SQLite.NET\bin\Designer</STRONG> folder and execute the <STRONG>INSTALL.CMD</STRONG> file. The script and batch file will register the System.Data.SQLite DLL in the Global Assembly Cache, |
︙ | ︙ | |||
117 118 119 120 121 122 123 124 125 126 127 128 129 130 | The SQLite3 source code is compiled directly from the SQLite.org release sources. All builds of sqlite after 3.2.8 have included support for Windows CE. Additionally, two minor modifications are made to the sources, those modifications are made automatically by the fixsource.vbs file when the VS2005 solution is compiled.</p> <p></p> <p> <b>Version History</b></p> <p><b>1.0.25.0 - January 31, 2006</b></p> <ul> <li>Code merge with SQLite 3.3.3</li><li>Added automatic distributed transaction enlistment and implemented the DbConnection.EnlistTransaction method for manual enlistment.</li> <li>Nested transactions are now supported.</li> <li>Rearranged the timing of SetPassword(), which now must be called before the database is opened instead of afterwards. Optionally, the password can be supplied | > > > > > > > > > > > > > > > > | 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 | The SQLite3 source code is compiled directly from the SQLite.org release sources. All builds of sqlite after 3.2.8 have included support for Windows CE. Additionally, two minor modifications are made to the sources, those modifications are made automatically by the fixsource.vbs file when the VS2005 solution is compiled.</p> <p></p> <p> <b>Version History</b></p> <p><b>1.0.26.0 - February 10, 2006</b></p> <ul> <li>Code merge with SQLite 3.3.4</li><li>Fixed an encryption bug when changing the password of databases over 1gb in size. </li><li>Fixed various designer issues related to construction of named parameters. </li><li>Implemented the SourceColumnNullMapping property of SQLiteParameter to fix a DbCommandBuilder code generation bug. </li><li>Removed the runtime dependency on MSVCR80.DLL. File size is somewhat larger for the varying desktop versions, but the Compact Framework version remains the same.</li><li>Created an install program to manage installation and uninstallation of the SQLite design-time support.</li> <li>Designer support now works for all Visual Studio editions, including all Express Editions.</li> <li>Design-time installer will now remove (if present) the machine.config SQLite entries in favor of installing the xml code into the devenv.exe.config file (or any of the variations for express editions). The officially-accepted behavior of using DbProviderFactories is to add the code to your app.config file, and the machine.config file should not be touched.</li> </ul> <p><b>1.0.25.0 - January 31, 2006</b></p> <ul> <li>Code merge with SQLite 3.3.3</li><li>Added automatic distributed transaction enlistment and implemented the DbConnection.EnlistTransaction method for manual enlistment.</li> <li>Nested transactions are now supported.</li> <li>Rearranged the timing of SetPassword(), which now must be called before the database is opened instead of afterwards. Optionally, the password can be supplied |
︙ | ︙ |