Comments on: Build Your Own Data Access Layer: Mapping Classes To Tables

By: Build Your Own Data Access Layer: Out Of The Box CRUD Functionality

Build Your Own Data Access Layer: Out Of The Box CRUD Functionality — Sun, 04 Sep 2011 11:16:07 +0000

[...] knows about your classes and your tables, CRUD operations should 'just work'.As you've seen in the previous post of this series, the TableInfo class offers a couple of methods to automatically build the required [...]

By: Build Your Own Data Access Layer: Bringing It All Together

Build Your Own Data Access Layer: Bringing It All Together — Sun, 04 Sep 2011 10:54:11 +0000

[...] (containing your entity types) will be used to to build up the metadata model as covered in the Mapping Classes To Tables post. You would typically call the Create method in your application's startup code, and then you'd have [...]

By: Mike Scott

Mike Scott — Thu, 27 Aug 2009 10:10:16 +0000

Hmmm, I used the code tag in my previous reply but it seems not to have honoured spacing, sorry

By: Mike Scott

Mike Scott — Thu, 27 Aug 2009 10:08:52 +0000

I know a dictionary lookup is an O(1) operation, but there’s no point in doing twice what you can do it once:

public static DbType ToDbType(Type type) { DbType dbType; if (!typeToDbType.TryGetValue(type, out dbType)) { throw new InvalidOperationException(string.Format("Type {0} doesn't have a matching DbType configured", type.FullName)); }

return dbType; }

By: New and Notable 362 : Sam Gentile's Blog (if (DeveloperTask == Communication && OS == Windows)

Tue, 25 Aug 2009 21:54:15 +0000

[...] on Build Your Own Data Access Layer Series. Some posts include Out of the Box CRUD Functionality, Mapping Classes to Tables, and Hydrating [...]

By: Ricardo Peres

Ricardo Peres — Mon, 24 Aug 2009 10:29:46 +0000

You are right, Davy, sorry!
I just read Oren’s comments also, this seems promising…

By: Davy Brion

Davy Brion — Mon, 24 Aug 2009 09:28:21 +0000

i actually talked about it in the post :p

search for “As for only targeting SQL Server,” and read the rest of the paragraph

By: Ricardo Peres

Ricardo Peres — Mon, 24 Aug 2009 08:58:44 +0000

Davy,

Nice post, as usual. I am looking forward for the next posts, because all tricky parts will come later on!
One think you didn’t address (and perhaps forgot to mention) was DB engine independence, your code requires SQL Server, am I right? What about creating an abstraction (or dialect) layer for dealing with different DBs, or, at least, leaving some extension points on the code?

By: Davy Brion

Davy Brion — Mon, 24 Aug 2009 04:47:44 +0000

@Jeremy

and writing a boatload of repetitive and error-prone code over and over and over again isn’t?

By: Venu

Venu — Mon, 24 Aug 2009 03:41:22 +0000

Thanks Davy. I think this is awesome.

I have been a user of NHibernate for a few years now and have not really taken the time to look under the hood. Also, I am going to be starting work at a place where the team have rolled out their own ORM/DAL. This gives me some perspective to compare and contrast.

By: Jeremy D. Miller

Jeremy D. Miller — Mon, 24 Aug 2009 00:48:21 +0000

Dude, you’re really depressing me with this series. You gotta do what you gotta do, but you’re still committing larceny against your customer — even if they’ve made you do it.