| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
| |
* Converted a bunch of functions to static functions.
|
| |
|
|
|
|
|
|
| |
settings as when an inventoryitems table is newly created
* Normalize logging titles in database code, though this doesn't yet cover invoking code
|
| | |
|
| |
|
|
|
|
|
|
|
| |
database adapter
* I don't use mssql so this may not work, corrections (in the form of patches) are welcome.
* Unlike mysql, mssql requires manual updating of existing tables here (which should mean just adding the new fields manually)
|
| |
|
|
|
|
| |
* Add updated stub mssql inventory sql (only really because I was in the middle of this when I spotted the numeric transposition)
|
| |
|
|
|
|
|
| |
Melanie!
RE: 0001079: r4387. touch() event does not fire when touch script is in root prim and child prims are touched
|
| |
|
|
|
|
|
|
| |
configs. This works with sqlite and nhibernate backends, and
stays with default seperate ini files for mysql and mssql until
someone writes those.
|
| |
|
|
|
|
|
|
| |
this will work for sqlite and nhibernate, but will be ignored for
mysql and mssql (reverting to their ini files) until someone writes
that bit.
|
| |
|
|
| |
(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. ::
|
| | |
|
| |
|
|
|
|
|
| |
grief than expected, as monodevelop doesn't like to refactor
properties of properties.
|
| | |
|
| |
|
|
|
|
|
| |
actually a little more work than I expected given the copious
use of out params.
|
| |
|
|
|
|
| |
to reflect what they really are.
|
| |
|
|
|
|
|
|
| |
* wrap attributes in properties
* clean up names a little bit
* clean up name styles
|
| |
|
|
|
|
|
|
| |
* wrap fields as Properties
* rename some fields/properties to more sensible names
* set style to PropName to match more standard C# approach
|
| | |
|
| |
|
|
|
|
|
| |
were implicitly included before). Everything builds again.
Now off to testing.
|
| | |
|
| |
|
