RE: #Of Topic

[Jeremy Gray]

Okay, I’ll bite. J   + Support Microsoft Application Blocks (Caching Configuration, DataAccess) I know of numerous developers who would see this dependency as a negative, not a positive. The application blocks are widely considered as powerful and beneficial but only as long as you buy into the whole package, which is often not desirable for many applications. For those applications, significant conceptual, configuration, deployment, and operational overhead awaits. In short, There Be Dragons. J   + The generated code allows make modifications in any level. Which reduces or nearly eliminates the benefit of code generation, already arguably minimal relative to metadata-driven solutions   + Support Framework 2.0 While not 100% official (that I’m aware of), ibatis.net is running on 2.0 in a number of environments, some VERY prominent.   + part of Visual Studio 2005 IDE via CodeSmith Not hugely relative at the end of the day, but you could say the same for ibatis.net once you have the xml schemas installed so that the IDE can see them   + Support DeepLoad (load the entitydata and all the entities related) Same for ibatis.net, complete with lazy loading, caching, etc.   The above are, of course, just my two bits. J   Jeremy     From: Decima, Mauro [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 04, 2006 4:08 PM To: user-cs@ibatis.apache.org Subject: RE: #Of Topic   If you use a MetaData Mapping, you need to update your metadata file when db Structure change, Nettier regenerate the base class. No magic there,  you can generate part or all the database. - I do not like that nettier generates a class by each table + Support Microsoft Application Blocks (Caching Configuration, DataAccess) + The generated code allows make modifications in any level. + Support Framework 2.0 + part of Visual Studio 2005 IDE via CodeSmith + Support DeepLoad (load the entitydata and all the entities related) + developed by this design http://msdn.microsoft.com/library/default.asp?url="">   I do not mean that it is better or worse than ibatis, it only wanted to share it with you so that they saw other options     Mauro         Just to provide some comments from someone other than the creator of the library J   -          Why generate code that has to be regenerated, recompiled, re-tested, and redeployed upon any database change? -          Code->schema generators lose critical control of the database, and are sensitive in upgrade and other version migration scenarios -          Schema->code generators are similarly problematic -          Why cripple both the class model and the database schema by settling on a lowest-common-denominator 1:1 literal mapping? -          Why generate anything when metadata will do? My developers can own the classes. The DBA team can own the database. The tool can bridge the gap, all without any-gen.     Jeremy Gray   From: Clinton Begin [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 04, 2006 2:46 PM To: user-cs@ibatis.apache.org Subject: Re: #Of Topic   Ack!  No offense, but this thing sounds like a nightmare.... Generates ready to use Visual Studio projects and solution. Fully integrate with Entreprise Library application blocks architecture. Shipped with it's own plugin, so you can configure your application directly from the entlib configuration console. No thank you....  ;-) Cheers, Clinton On 4/4/06, Decima, Mauro <[EMAIL PROTECTED] > wrote: I have see http://www.nettiers.com. This is a great job     .NetTiers are CodeSmith templates for object-relational mapping that takes an existing SQLServer database and automatically generates a personnalized Data Tiers application block to use in your .Net applications.