Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | * Optimised using statements and namespace references across entire project ↵ | Adam Frisby | 2008-04-21 | 1 | -1/+0 |
| | | | | (this took a while to run). | ||||
* | * Discerned between AddProfile and UpdateProfile in region registration | lbsa71 | 2008-04-11 | 1 | -0/+2 |
| | | | | | :: 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 |
| | |||||
* | reorganizing namespaces to put all the Data stuff into it's own namespace | Sean Dague | 2008-04-02 | 1 | -0/+118 |
/ dir structure. This is coming in over a few changesets so consider trunk broken for the next 30 minutes as these get pulled together. |