BUY Clarina Cream ONLINE WITHOUT PRESCRIPTION http://elegantcode.com/2008/08/12/orm-value-reason-3982/?utm_source=rss&utm_medium=rss&utm_campaign=orm-value-reason-3982 Tue, 08 May 2012 09:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 BUY Clarina Cream ONLINE WITHOUT PRESCRIPTION http://elegantcode.com/2008/08/12/orm-value-reason-3982/comment-page-1/#comment-29634 Chris Brandsma Tue, 12 Aug 2008 19:32:51 +0000 http://elegantcode.com/2008/08/12/orm-value-reason-3982/#comment-29634 @Tobin: I am 100% with you on the "95% of the time" comment. To be fair, you almost have to break up ORMs into two categories: those that create the mappings for you (SubSonic, LINQ to SQL, etc), and those that require you to create the mappings (NHibernate, ...). I was mainly referring to the first type. Although, because of the syntax with the mapping files, it is still much harder to make that mistake. If you look at an NHibernate property mapping (using the hbm files), both the column and the property will be mapped together on the same entry. Plus the order of the properties in the mapping file doesn't matter. Nor does the order in which you set the properties on the object you are about to save. Where as with an INSERT statement, the order of the column and the data being passed in must be exact, plus the two items are not right next to each other (in SQL, I put them on separate lines so I can sort of visually match them up). This is just one, of many, ways that I believe that SQL stinks as a language. @Tobin: I am 100% with you on the “95% of the time” comment.

To be fair, you almost have to break up ORMs into two categories: those that create the mappings for you (SubSonic, LINQ to SQL, etc), and those that require you to create the mappings (NHibernate, …).
I was mainly referring to the first type. Although, because of the syntax with the mapping files, it is still much harder to make that mistake.

If you look at an NHibernate property mapping (using the hbm files), both the column and the property will be mapped together on the same entry. Plus the order of the properties in the mapping file doesn’t matter. Nor does the order in which you set the properties on the object you are about to save.

Where as with an INSERT statement, the order of the column and the data being passed in must be exact, plus the two items are not right next to each other (in SQL, I put them on separate lines so I can sort of visually match them up).

This is just one, of many, ways that I believe that SQL stinks as a language.

]]> BUY Clarina Cream ONLINE WITHOUT PRESCRIPTION http://elegantcode.com/2008/08/12/orm-value-reason-3982/comment-page-1/#comment-29631 Tobin Harris Tue, 12 Aug 2008 18:18:27 +0000 http://elegantcode.com/2008/08/12/orm-value-reason-3982/#comment-29631 Actually, you could screw up your mapping file and get the columns the wrong way around :) The ORM might catch this at "warm up" time as it's interpreting the mapping file. I might be being dim here (it's been a long day), but which ORM do you know which captures this at compile time? I wouldn't be too hard on yourself for not using an ORM though, I love em only 95% of the time :) Actually, you could screw up your mapping file and get the columns the wrong way around :) The ORM might catch this at “warm up” time as it’s interpreting the mapping file. I might be being dim here (it’s been a long day), but which ORM do you know which captures this at compile time?

I wouldn’t be too hard on yourself for not using an ORM though, I love em only 95% of the time :)

]]>