| Commit message (Collapse) | Author | Files | Lines |
|
Thank you, RuudL, for a patch that brings MSSQL up to the same
implementation level as MySQL.
|
|
* This is a HUGE OMG update and will definitely have unknown side effects.. so this is really only for the strong hearted at this point. Regular people should let the dust settle.
* This has been tested to work with most basic functions. However.. make sure you back up 'everything' before using this. It's that big!
* Essentially we're back at square 1 in the testing phase.. so lets identify things that broke.
|
|
|
|
(issue 1763).
|
|
|
|
(this took a while to run).
|
|
|
|
:: Believe it or not, but INSERT/UPDATE is actually a better pattern than REPLACE, since, with INSERT/UPDATE you can catch erroneous UPDATES to non-INSERTed items as well as catch erroneous re-INSERTS. in 95% of the cases, you SHOULD have a clear INSERT context, and a clear and separate UPDATE context. If you think your case falls within the 5%, maybe you should re-evaluate your code. ::
|
|
|
|
/ dir structure. This is coming in over a few changesets so consider trunk
broken for the next 30 minutes as these get pulled together.
|
|
|
|
|
|
* changed the semantics of SQLiteBase to SQLiteUtils
* Added abstract placeholder files for the other db providers
|