The manuals says this:
Note! Parameter Map names are always local to the SQL Map XML file that
they are defined in. You can
refer to a Parameter Map in another SQL Map XML file by prefixing the id of
the Parameter Map with the
id of the SQL Map (set in the sqlMap root tag). For example, to refer
operations (select, update,
delete etc.)?
Thanks
Jeff
Jeff P wrote:
The manuals says this:
Note! Parameter Map names are always local to the SQL Map XML file that
they are defined in. You can
refer to a Parameter Map in another SQL Map XML file by prefixing the id
of the Parameter Map
Hello.
My application is using iBatis' method querForList. However, after I
execute this method my memory useage sky-rockets upwards. I have profiled my
application and it happends when I execute the following method:
public static ListCity selectUnsyncedCityByDate(SyncDates syncDates,
int
Sorry for forgetting to mention that.
I'm using MySQL with MyConnectorJ5.1.7
I've tried a test with the Rowhandler and unfortunatly memory also jumps up
tremendously after the database connection has been established (5mb to
50mb).
Larry Meadors wrote:
This *really* depends on the JDBC
For what its worth... my profiler says the 3 biggest memory hogs are:
byte[] (65%)
byte[][] (20%)
com.mysql.jdbc.ByteArrayRow (10%)
I've attached a screenshot of the profiling results.
Perhaps this rings a bell?
Thanks!
http://www.nabble.com/file/p21568927/profiling_results.png
--
View
this problem if the driver does this.
Larry
On Tue, Jan 20, 2009 at 11:34 AM, Jeff P killingd...@hotmail.com wrote:
For what its worth... my profiler says the 3 biggest memory hogs are:
--
View this message in context:
http://www.nabble.com/Excessive-memory-usage-%28feature-or-bug-%29
I want to feed my client the database/table creation queries. However iBatis
doesnt seem to execute them right. My method looks as the following:
public static void createDatabase(String sqlString) throws SQLException
{
BaseSqlMapper.sqlMapper.insert(createDatabase, sqlString);
}
Inside my
Solved!
And to think I spend an hour on mistyping just two simple characters...
Thank you very much!
--
View this message in context:
http://www.nabble.com/Create-statement-used-wrongly--tp21669143p21671212.html
Sent from the iBATIS - User - Java mailing list archive at Nabble.com.
I was in the process of stresstesting my app and found out that my count
queries weren't optimal. I've produced the following JDBC test and iBatis
test and the test says iBatis is 6 times slower.
I know iBatis should be just as fast as JDBC, so I refuse to accept that
outcome. However I can't
. We're talking
milliseconds usually.
Cheers,
Clinton
On Sun, Mar 22, 2009 at 8:13 PM, Jeff P killingd...@hotmail.com wrote:
I was in the process of stresstesting my app and found out that my count
queries weren't optimal. I've produced the following JDBC test and iBatis
test and the test says
Also, a detail that might be of interest is the following:
Supersmack allows the user to specify the amount of connections. When I
configure 1 user to stresstest, the queries per second are arround 50K. When
I configure 2 users to stresstest, the queries per second go to 70-80K. This
is logical,
11 matches
Mail list logo