5 Kicks

Data Access in Fail Tracker(trycatchfail.com)

submitted by Matt_TCFMatt_TCF(946) 9 months, 23 days ago

This is the first in a series of short posts on how data access is handled in Fail Tracker. Future posts will get into how the strategy works with unit testing as well as how advanced topics, such as row-level security, are handled. Read on to find out how Fail Tracker utilizes a simple repository layer around NHibernate for all data access.

1 comment |category: |Views: 9

tags: another

new Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

  • "Kick It" text
  • "Kick It" background
  • kick count text
  • kick count background
  • border

Simply copy and paste this HTML into your blog post.


Users who kicked this story:
lukianlukian(5) - bsenoffbsenoff(1583) - geniustouchgeniustouch(0) - dpetersondpeterson(4397)
More who kicked this story...
Comments:

posted by dpetersondpeterson(4397) 9 months, 22 days ago 0

I noticed in the repository you implemented that you included a Save method.
It seems like lots of people these days are creating repositories that combine both the repository pattern (http://martinfowler.com/eaaCatalog/repository.html) and the unit-of-work pattern (http://martinfowler.com/eaaCatalog/unitOfWork.html).

Would testing ability be helped or hindered by having greater separation of concerns and splitting the repository you have implemented into separate objects (more strictly following the repository and unit-of-work patterns)?

Thanks for sharing :-)

Reply

information Login or create an account to comment on this story
Submit a Story
View upcoming stories
How else can I help?
Add our feeds to your site

Most Active Users

What's this?