O/R mappers and generator
I’ve been doing a moderate amount of research into tools that generate data access layers, entity or object tiers, and other layers for enterprise (or non-enterprise) applications. One of the tools I’ve picked up lately per some encouragement from a coworker is LLBLGen Pro. One can download a demo at the LLBLGen site to try out.
LLBLGen Pro is claimed as the #1 O/R Mapper (I’m not sure this is true, I haven’t seen sales statistics) for the data-access tier in .NET. The tool can be used against Access, PostgreSQL, Oracle, mySQL, DB2, and of course SQL Server 7.0 or greater. At the same time support is given to the databases, the code generated is independent of the specific database, and for type differences (such as Oracle’s lack of a Boolean type) type converters can be created.
The tool also creates typed lists for entity fields based on one to one, one to many, or many to one relationships. LLBLGen Pro will also create typed views one one to one mappings, support existing stored procedures with wrapper code which enables a single line of code for calling. The tool also will accept templates for other peripheral code generation as needed. For more information on the features, hit the LLBLGen Features List. For tutorials, videos, and samples check out the tutorials page.
As my ranting has ensued about non-use of code generation, the LLBLGen site lays out the facts right on the main page. LLBLGen Pro (or really, ANY code generator) will save a huge portion of a project’s development time. The site puts the number at 50%, I’d put it even higher with a high confidence on my proclamation. As I’ve often complained about the endless boiler plate code, this tool easily replaces greater than 90% of that, the rest easily removed by good use of object oriented pattern based design practices.
The tool swings in at a relatively cheap 229.99 Euro starting price, which as of this date translates to $308.57. ![Big Smile [:D]](/emoticons/emotion-2.gif)
Next I will probably toss in some reviews of .NET Tiers, NHibernate, and other such tools just for good measure.
My code compiles, so can I take a break? I love those xkcd strips! ![Smile [:)]](/emoticons/emotion-1.gif)
I got up super early this morning to knock some last minute code out before a deliverable was due today. So here I am this morning about 4:45am wondering about getting some coffee. Of course it is Portland and there are several places I could just up and go to, one is even within 10 minutes of walking. But I just recently bought a bag of Peet’s Coffee and I’m in the mood for Peet’s Coffee. So I start digging around for filters and all that jazz.
Well all of a sudden I run into a show stopper, I have no creamer, milk, or any other substitute. So now I have to go to the store, but wait. I all of a sudden have a strange developer type idea to use something that already inherits some similar values to sugar AND creamer! I’ll use ice cream!
Thus I have ice cream sweetened and creamed coffee this morning. I must say, if you like the taste of ice cream and coffee without anything in it, this is not a bad combination. I might even try it when I have alternatives! So without breaking my developer mind set for more than 5 minutes I make and have myself a cup of coffee. With that cup of coffee sitting by my side I then continue with the coding trance!
I’ve been working with a standard .NET Windows Application and have had some of the oddest binding behaviors. I seem to be getting “ghost” refreshes of data when exiting text boxes, and writes of previously entered data. This got me thinking, why am I actually using binding? It isn’t always the best choice and often times seems to be sub-optimal, especially when one has to programmatically keep up with the state of data anyway.
I’ve been looking around for some alternate patterns and ideas behind binding. Is there any factories out there that take data and controls and produce a bound control? Is there a pattern that would work for me to auto map data to controls without using the in place binding? Either which way I’m contemplating just coming up with a “from scratch” solution for fun.
For now, I just wanted to randomly write about binding, to kind of work up a direction in my head to work forward with. I think now though that I’m going back to troubleshooting the transit related application I’ve been working on. So this inquiry… …has limited interest… …and will for a short period more.
I’ve heard this, often said tongue in cheek, “If people realized how simple software development was, it would be a minimum wage occupation.” Of course it changes slight when said from person to person. The main point is there, that somehow, someway, software development is easy. I think it is easy, and many developers I’ve worked with, find it easy.
I sat and thought about this for a while during a re-reading of “Refactoring – Improving the Design of Existing Code” and came to a simple and straight forward conclusion. Software development is easy to us software developers because we do it, because we’ve learned the processes, we are enraptured by the multi-faceted, multi-process, brainy work that it is, and we excel because we “software developers” are obsessive compulsive learners.
News flash, the general populace does not embody any of the listed characteristics. The slightly above average IQ isn’t even in the cast of “obsessive learner”. They aren’t even remotely interested in multi-faceted, multi-process, and brainy work. This left me with a solace of some sort, the average person, even the above average person, even the witty fellow that seems to know a bit of everything is not going to come take over the software industry and drop the wage rates of software development. Even the initial off-shoring of American Software Development has wavered in the simple fact that Americans are relatively good at software development. You can’t introduce this occupation to average people or cultures that don’t inherently accept obsessive traits and individualistic perseverance like the software industry does. We excel at building and creating “new” things. Sometimes we have a hard time picking up good process, lean and agile, sometimes we bump our heads on the “stupid block”, but the average man isn’t going to intrude upon this industry. The cultural and personal characteristics of the software developer are just not easily duplicated.
So to summarize, employers aren’t going to get people cheap anytime soon, software isn’t free no matter what license is included. Somebody is going to do the work, and those software grognards aren’t remotely average. The software people need to remember, that we aren’t average, and thus stepping out of self mindset and looking at one self from another perspective is important. The two main things, don’t underrate one self and don’t overrate, know and work diligently to keep up with where you stand in the industry.
Period. ![Cool [H]](/emoticons/emotion-11.gif)
