Hey Vic, No worries. We're not taking away the XML. We are simply introducing a new Dynamic SQL syntax. If your DBAs can handle the new stuff, great. If not, then they can stick with the old stuff. In most projects, competent developers (DBA or otherwise) will be writing the SQL, so we have to take care of the majority.
As for JDO, that's got a big -1 from me. JDO is the ugliest thing walking the O/R planet if you ask me. I'd choose Hibernate or TopLink over JDO, without question. Clinton On Wed, 02 Feb 2005 15:52:45 -0600, Vic Cekvenich <[EMAIL PROTECTED]> wrote: > Storing SQL outside in XML is key, so DBA can get to it. > I also think that a JDO like wraper arround SQL maps would be cool. Some > people think that iBatis is not "standard". > .V > Wana read a Vic rant on O/R: http://www.sandrasf.com/node/35 > > Clinton Begin wrote: > > >If we stray > >from XML and choose a predominantly Java-ish language to support > >(Velocity, Groovy etc.) there could be concerns around the uniformity > >and consistency of our product accross platforms. > > > > > > -- > Forums, Boards, Blogs and News in RiA <http://www.boardVU.com> >
