[SNIPPED] > > Your patch to the TableTool in TorqueDataDump worked for me > with sybase, but > > mysql hung. I took the easiest way out which was to > re-implement that inner > > class using Village. This effectivly reads the entire > result set into a > > QueryDataSet which allowed the Iterator interface to be implemented > > correctly. Not much different but has some trade offs. > The first being the > > entire dataset is read into memory: large tables will suck. > The other is > > since Torque is currently implemented with Village, the > data dump task will > > work with any jdbc driver that village ( and subsequently > torque ) works > > with. > > Strange it didn't work with mysql. I tested it with mysql > before I sent > it in. Are you using the mm.mysql-2.0.7-bin.jar? I had to change > TableTool because it was using the ResultSet.isLast() method which is > not supported by jConnect (Sybase seems a little behind in JDBC 2.0 > compliance). However, it sounds like the change you made has the best > chance of working with the assortment of JDBC drivers. What are your > thoughts about memory usage when exporting data? Loading all the data > into the ResultSet could be a strain. I was using 2.0.4, and yea, memory usage will be a problem with huge tables that you want to dump to xml.
<NOTPOSITIVE> I believe the mm.mysql driver loads the resultset into memory already anyway, so the issue was there to begin with ( for mysql anyway ). </NOTPOSITIVE> Since the data dump stuff wasn't working for sybase, we rolled our own targets in our build and use bcp to copy the data local and post it back up. For huge tables the local xml file would be gigantic anyway. Maybe TDD is a tool for smallish tables and for full data transfer of entire systems, you'll need to roll your own solution? > > Could you, or anyone else, try this out? I've tested it > with sybase and > > mysql and all seems OK here. Thanks. > > > > jb > > > > I tested it with sybase and mysql and both ran ok. > +1 for the patch. > > Byron > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
