Dylan Smith

ALM / Architecture / TFS

  Home  |   Contact  |   Syndication    |   Login
  72 Posts | 0 Stories | 115 Comments | 29 Trackbacks

News



Archives

Post Categories

Blogs I Read

July 2006 Entries

We have a problem to solve to do with making subledger/GL entries. This is a problem that I'm positive has already been solved in every accounting/ERP package out there....I just can't seem to find anybody who knows the answer. When certain events occurs in our ERP system, we need to make a number of entries to our GL. A transaction may have multiple debits and credits split up over multiple accounts. The sum of all the debits must equal the sum of all the credits. The problem is that these entries ......

I was reading a post on Rob Caron's blog where he links to a few posts by Sachin Rekhi (a program manager from the Data Dude team). There are a number of posts about how the new database unit testing features work, and he walks you through implementing a database unit test. My opinion is that the database unit testing functionality isn't very valuable as it stands today. It appears targetted to allow you to test a very limited set of conditions: the row count, a scalar value returned, a empty/non-empty ......

I was just writing some wrapper code for our database access layer, and I noticed that ExecuteNonQuery seems to be behaving differently than I thought it behaved. It says it returns the count of the records affected. I had thought that if you were executing multiple queries in your stored proc, it would return the records affected by only the last query. However, it appears to be returning the sum of the records affected from all queries. Is this something that has changed in .Net 2.0, or maybe in ......

I've been continuing my research and experimentation with TDD lately. For my tests that actually hit against the database (as opposed to the ones where I mock the database layer), I need to ensure that the database is in a reproducable state to ensure that the test itself is reproducable. I figured the best way to do this was to just re-create the database automatically every time my unit tests ran (well the ones that hit against the database anyways). I need to recreate not only the database schema ......

Yet another problem I have had to address recently is the issue of state recreation. We require the ability to go back and "audit" or review decisions that were made in the past. A common situation that comes up, is we as a company get into a pickle. To help prevent the situation from happening again we investigate the problem to get a better understanding of the cause. We trace back the root cause to a decision or a number of decisions that were made in the past. This may be decisions to change ......

For Authorization we had the requirements that we had to be able to easily assign a specific user to a certain "role" and they would have all the priveledges associated with that role. We had to be able to make users members of multiple roles. We also had to be able to configure what specific priveledges belonged to each role. In addition, we had to be able to assign a specific user to a specific role, but then also give them access to one or more specific priviledges in addition to those granted ......