RE: #Of Topic

[Jeremy Gray]

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.