Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | let Grid Servers specify a connect string in their configuration. | Sean Dague | 2008-05-28 | 1 | -1/+2 |
| | |||||
* | Formatting cleanup. | Jeff Ames | 2008-05-16 | 1 | -9/+9 |
| | |||||
* | * Thanks to Mic Bowman for inspiring me to look at that we are still using ↵ | Adam Frisby | 2008-05-01 | 1 | -1/+1 |
| | | | | ASCIIEncoder in places we shouldn't. | ||||
* | * Align new fields upgrade sql to have the same 'not null' and default ↵ | Justin Clarke Casey | 2008-05-01 | 1 | -3/+3 |
| | | | | | | | | settings as when an inventoryitems table is newly created * Normalize logging titles in database code, though this doesn't yet cover invoking code | ||||
* | * Optimised using statements and namespace references across entire project ↵ | Adam Frisby | 2008-04-21 | 1 | -2/+3 |
| | | | | (this took a while to run). | ||||
* | * Discerned between AddProfile and UpdateProfile in region registration | lbsa71 | 2008-04-11 | 1 | -8/+73 |
| | | | | | :: 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. :: | ||||
* | attempt to fix up all refernces to new directory structure | Sean Dague | 2008-04-02 | 1 | -1/+1 |
| | |||||
* | whole lot more moving | Sean Dague | 2008-04-02 | 1 | -0/+366 |