I have found where a root entity has completed processing and added the
logic to clear the entity's cache at that point (didn't change any of the
logic for clearing all entity caches once the import has completed). I have
also created an enhancement request found at
By placing some strategic debug messages, I have found that the JDBC
connections are not being closed until all entity elements have been
processed (in the entire config file). A simplified example would be:
dataConfig
dataSource name=ds1 driver=org.postgresql.Driver
Gora,
Thanks for the response. After taking another look, you are correct about
the hasnext() closing the ResultSet object (1.4.1 as well as 1.4.0). I
didn't recognize the case difference in the two function calls, so missed
it. I'll keep looking into the original issue and reply if I find a
On Sat, Jan 8, 2011 at 1:10 AM, Shane Perry thry...@gmail.com wrote:
Hi,
I am in the process of migrating our system from Postgres 8.4 to Solr
1.4.1. Our system is fairly complex and as a result, I have had to define
19 base entities in the data-config.xml definition file. Each of these
Hi,
I am in the process of migrating our system from Postgres 8.4 to Solr
1.4.1. Our system is fairly complex and as a result, I have had to define
19 base entities in the data-config.xml definition file. Each of these
entities executes 5 queries. When doing a full-import, as each entity
This is my configuration which seems to work just fine.
?xml version=1.0 encoding=utf-8 ?
dataConfig
dataSource type=JdbcDataSource
name=DBImport
driver=net.sourceforge.jtds.jdbc.Driver
url=jdbc:jtds:sqlserver://localhost;databaseName=50_DEV;responseBuffering=adaptive;
