doc for 2.1 version

Hi, Im looking for ibatis ver 2.1 docs, in the site only are 2.0 docs. I like to know more about resultmap, resultmap and group by attributes. Im working with Oracle 10g and have some problems with non Resul Set OUT an INOUT parameters too. Thank you Wilberto Montoya Lima- Peru

Re: Best mechanism to read large datasets

On 7/8/05, Michał Małecki <[EMAIL PROTECTED]> wrote: > ...hopefully you can write it in Java ;) Why does it matter? Code is code... ;-) Larry

Re: Best mechanism to read large datasets

I absolutly agree,queryWithRowhandler was my first shot, but if possible, stored procedure is the right solution; hopefully you can write it in Java ;) Michal Malecki Using queryWithRowhandler() as Michal suggested is the iBATIS solution. That said, I would seriously consider doing the proce

Re: Best mechanism to read large datasets

Using queryWithRowhandler() as Michal suggested is the iBATIS solution. That said, I would seriously consider doing the process with a stored procedure if possible. You will get WAY better performance, and reduce network traffic significantly. Larry On 7/8/05, Rao, Satish <[EMAIL PROTECTED]> w

unsubscribing via the mailing list webpage

I was looking on the mailing lists page for iBatis to see if there was a mechanism for unsubscribing. Is there a mailto: address that can be used to easily unsubscribe from the user-java list? I don't seem to have the original email which described how to unsubscribe from the list.

Re: Best mechanism to read large datasets

Title: Best mechanism to read large datasets Can you explain or anyone else, how it works or what is the best practise? I think that statement is open, and for each row method public void handleRow (Object object);  is invoked or something like that   I assume, that we want to process a lar

Re: Building iBATIS_DBL-2.1.0.565

You can also compile to JDK 1.4 in WSAD if you want to. Simply install a 1.4 JRE somewhere (or use the WAS 5.1 JRE if you have it installed), then point your project to it. If the iBATIS project is part of an EAR project, you can use WSAD's server targeting support to target WAS 5.1 - then you'll

Re: Best mechanism to read large datasets

Title: Best mechanism to read large datasets Hello, I think queryWithRowHandler should do the trick :)   Regards Michał Małecki- Original Message - From: Rao, Satish To: user-java@ibatis.apache.org Sent: Friday, July 08, 2005 4:10 PM Subject: Best mechanism to read l

RE: Best mechanism to read large datasets

Title: Message I would definitely like that, but unfortunately, that is not an option. -Original Message-From: Darek Dober [mailto:[EMAIL PROTECTED] Sent: Friday, July 08, 2005 10:16 AMTo: user-java@ibatis.apache.orgSubject: Re: Best mechanism to read large datasets Ca

Re: Best mechanism to read large datasets

Title: Best mechanism to read large datasets Can't you divide your result into pages with smaller number of records ?   queryForList with proper parameters should do that.   Darek - Original Message - From: Rao, Satish To: user-java@ibatis.apache.org Sent: Friday,

Re: Building iBATIS_DBL-2.1.0.565

You have to compile with JDK 1.4.  Once compiled, it should work with 1.3 as well. Your best bet is to : 1) Download and install JDK 1.4 2) Set your JAVA_HOME to the install dir of JDK 1.4 3) Checkout the iBATIS source from the Subversion repos 4) Make your changes. 5) Run build.bat. ClintonOn

Best mechanism to read large datasets

Title: Best mechanism to read large datasets I have a situation where I might be retrieving thousands of rows from Oracle. I am using a queryForList() and I am assuming it stores the rows in memory. As a result I am quickly running out of memory. Is there a way for ibatis to read each row fr

How to set the connection read-only?

  Is there a way to set the connection in the read-only state before starting a transaction? I'm using a mix of DAOs and sqlMaps in my application so I'm interested in a solution for both of them.   Thanks, Florin  

SV: SAXParseException, parsing the sqlMap-config.xml file!

Hi there! >Apparently you have an element type that is not in proper order with the DTD. You are right, after downloaded the JEdit (thanks for the tip) with the xml parser plugin, tested with the sqlMap-config file from the sqlMap pdf file ... I found out it was the order. I had it like this:

RE: ResultSet metadata

I've got a similar problem. I have a immutable Quantity object that takes two arguments for its constructor. No of the Quantity properties can be populated using setter methods. I would like to use a custom type handler to construct the object. Doing reflection on the result set will not alw