2 Kicks

Linq query or plain SQL? On using tools for what they are made for.(notherdev.blogspot.com)

submitted by notherdevnotherdev(238) 6 months, 8 days ago

There are some scenarios where using NHibernate.Linq makes no sense. NHibernate's provider is just a tool, with its design, its features and its limitations. It's important to be aware what each tool is the best at and not to look for universal tool.

1 comment |category: |Views: 27

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:
dpetersondpeterson(4397) - notherdevnotherdev(238)
Comments:

posted by dpetersondpeterson(4397) 6 months, 7 days ago 0

I feel many developers make the mistake of ignoring SQL. Like you said, when fetching business objects, work with your ORM; otherwise, you should probably look into SQL. I think mass updates are a situation where it pretty much never makes sense to use your ORM for the task, and an easy dividing line for developers who are unexperienced with data access to go by.

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?