Absolutely. iBATIS 2.0 came with a compatibility kit back to 1.x that
allowed you to either convert your SQL Maps statically, or have them
converted dynamically at runtime so you could use 1.x maps and code with the
2.0 engine...
While I was proud of that, it did keep me from doing a few things I
Yes, please keep backwards compatability within minor releases.
-Original Message-
From: Clinton Begin [mailto:[EMAIL PROTECTED]
Sent: Wed 1/30/2008 6:11 PM
To: user-java@ibatis.apache.org; [EMAIL PROTECTED]
Subject: RE: Exit out of rowHandler
Hehe...
Well, considering how much effort I
Hehe...
Well, considering how much effort I've always put into iBATIS being backward
compatible, why break tradition now? ;-) We can use an adapter and create
a new RowHandler interface.
iBATIS 3.0 can merge them into one...as it won't be fully backward
compatible anyway.
Clinton
-Ori
Meh, it'll break compatibility, but it adds a great deal of useful
functionality for very little cost. In addition, the 'fix' is to add a
"return true;" to existing code. I wouldn't consider that particularly
onerous...unless you have like 1000 row handlers, in which case, you
probably *deserve* so
Perfect. That was it!!! I changed it to float and it worked. Thanks a
lot for your help Jeff. I truly appreciate your fast response too..
Sundar
From: Jeff Butler [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 30, 2008 2:55 PM
To: user-java@ibatis.apache.
NUMBER is not a valid jdbcType - that's at least one problem. Obviously,
this is not so critical on the IN parameters, but it causes problems for the
OUT/INOUT parameters. A java.lang.Long would typically correspond to
jdbcType BIGINT.
See java.sql.Types for valid jdbcTypes.
You're also asking
I can't think of any other use for the return value, so I like the idea.
The only drawback is that this will break existing row handlers. This could
be an argument in favor of the two parameter approach - because it could be
an overloaded method. Of course, any change to the interface is going to
Thanks for the immediate response Jeff.
My sql-map is something like this.
{call example(?,?,?,?,?,?,?,?,?,?,?)}
The last 2 params are float in the Database. I am not sure if this has
something to do with the procedure returning multiple out params.
Make sure you are specifying the jdbcType of the out/inout parameters in
your parameter map.
Jeff Butler
On Jan 30, 2008 3:37 PM, Sundar Sankaranarayanan <
[EMAIL PROTECTED]> wrote:
> Hi All,
> I have a stored procedure, which is something like this.
>
> call example(?,?,?,?,?,?)
>
> The first
Hi All,
I have a stored procedure, which is something like this.
call example(?,?,?,?,?,?)
The first four params are IN params and the last 2 are out params. If I
set the mode="OUT" or set the mode as "INOUT" in the sql-map xml file I
get a
--- Cause: java.sql.SQLExceptio
Actually, it is even harder -- we'd like to use Lazy Loading of the
associations into this hierarchy. I think that means we could not use a
RowHandler, anyway...
On 1/30/08, Hugh Ross <[EMAIL PROTECTED]> wrote:
>
>
> Good indexing, but Outer Join required. We are OK with discriminator for
> our
Good indexing, but Outer Join required. We are OK with discriminator for
our smaller hierarchies, but unfortunately we have some large ones, too.
On 1/30/08, Clinton Begin <[EMAIL PROTECTED]> wrote:
>
> If it's an inner join, properly indexed, it shouldn't be too bad
>
>
>
> *From:* Hugh Ro
If it's an inner join, properly indexed, it shouldn't be too bad
From: Hugh Ross [mailto:[EMAIL PROTECTED]
Sent: January-30-08 12:36 PM
To: user-java@ibatis.apache.org
Subject: Re: Safe to replace valueObject in RowHandler?
Yes, we have begun experimenting with discriminators and su
Yes, we have begun experimenting with discriminators and subMaps. But, I
want to avoid a 15 table join...
On 1/30/08, Clinton Begin <[EMAIL PROTECTED]> wrote:
>
> Unfortunately that's not possible in Java, let alone with iBATIS.
>
>
>
> If you're just trying to create subclasses based on a type
I have associations at various levels of the hierarchy. Some of which are
"many." I'm trying to avoid having one huge join for all the possible
sub-classes. Yes, a bunch of smaller queries would be preferred. (Assuming
they don't repeat/overlap each other a lot.)
On 1/30/08, Christopher Lamey
Hmmm... would it be horrible if the return value of handleRow() was a
boolean for "continue"?
// don't mind the verbosity or any misplaced
// capital letters...thank you outlook
public boolean handleRow (Object valueObject) {
boolean continue = true;
if (someCondition) {
continue = false
Here is the code that is causing the memory leak:
sqlMapClient.queryWithRowHandler("getSomeList", queryObject, this);
public void handleRow (Object valueObject)
{
;
}
As you can see, I do nothing except issue the query. my "handleRow" is
empty and it eventually runs out of memory
Yuvraj ,
The ibatis community would need a while lot more information from you to
even start to assess your issue.
You gave us nothing to start with so our response will not be much more then
that.
Nathan
On Jan 29, 2008 5:14 AM, Niels Beekman <[EMAIL PROTECTED]> wrote:
> Maybe you're typing
I too have used RH'ers over very large data sets and never saw any memory
issues. Be careful when issuing statements like "And there is absolutely no
doubt that the culprit is ibatis". I can't tell you how many times we have
seen claim of ibatis failures only to find our that it was not.
Give u
You are absolutely right - I can let it ride it out. And I would agree
with you if the query came back within a second or two. But million
rows don't come back that quickly and the user will want to continue
with other operation after they cancel. Unfortunately, all buttons are
disabled during t
So are you basically looking at one big query with a bunch of joined tables
or a bunch of smaller queries to pull it all together?
If so, which one would fit better for your app?
On 1/29/08 6:42 PM, "Hugh Ross" <[EMAIL PROTECTED]> wrote:
> I have the good fortune to work on a large domain model,
Interesting - I don't think I used a groupBy with my large volume
RowHandlers.
If you're writing to the output stream from the RowHandler and the user
Cancels the download, wouldn't the stream get closed and cause an exception
the next time you tried to write?
It seems like you're going through a
Thanks - that's good to know. That gives me a warm fuzzy feeling.
I guess the issue now is to figure out what type of query in ibatis is
causing the memory leak. And there is absolutely no doubt that the
culprit is ibatis. JDBC with the same query left no residue of memory
leaks. And rearrangi
Seconded - great book.
parki...
From: Brandon Goodin [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 30, 2008 11:36 AM
To: user-java@ibatis.apache.org
Subject: Re: Safe to replace valueObject in RowHandler?
Or you can buy iBATIS in Action...
http://www.
It's not safe. If you have to return a value from "handleRow",
introduce a private variable.
private Person newPersonFromHandleRow;
public void handleRow(Object valueObject)
{
Person person = (Person) valueObject;
newPersonFromHandleRow = MyFactory.createSubClassObject( person );
}
But out of
Or you can buy iBATIS in Action...
http://www.amazon.com/iBatis-Action-Clinton-Begin/dp/1932394826/ref=pd_bbs_sr_1?ie=UTF8&s=books&qid=1201710921&sr=8-1
On Jan 30, 2008 10:29 AM, Clinton Begin <[EMAIL PROTECTED]> wrote:
> Unfortunately that's not possible in Java, let alone with iBATIS.
>
>
>
>
What exception?
Jeff Butler
On Jan 29, 2008 11:51 PM, Hemant. Kamatgi <[EMAIL PROTECTED]> wrote:
> Hi All,
>
>
>
> I'm getting an exception when trying to execute a dynamic sql in iBATIS.
> The query is below:
>
>
>
>resultMap="patternAttributeResult">
>
> select ptrn_i,ptrn
+1 to Jeff, those settings have already been removed from the trunk.
Use EXTERNAL if you're using EJB or Spring (or any other transaction capable
container), or JTA if you're using iBATIS alone with XA connections.
Otherwise, using JDBC should work fine too.
Clinton
Clinton
From: J
Unfortunately that's not possible in Java, let alone with iBATIS.
If you're just trying to create subclasses based on a type column in the
database, look up "discriminator" in the ibatis documentation or mailing
list archives...
Clinton
From: Hugh Ross [mailto:[EMAIL PROTECTED]
Sent:
Trying to be more specific:
Is it safe to create another object in the handleRow method, and set the
valueObject to it?
Is it safe to use queryForObject from within a handleRow method? I've seen
other posts that imply it is.
Will that object then replace the original one, if it was created by a
We recommend getting rid of maxRequests, maxSessions, maxTransactions -
these values will no longer be supported in the next version of iBATIS. In
your case (using a JNDI connection pool with WebSphere), you should set all
these things on the datasource configuration in WebSphere.
Also, it's prob
Did anyone had a chance to look into my query ? This is causing a major issue
with the application I am working on in production and any help is highly
appreciated.
BTW , the transaction is defined as CMP and we use websphere 5.1 as
application server.
Let me know if anyone has faced similar kin
try:
select ptrn_i,ptrn_n from $schema$.eprs_ptrn
ptrn_statc_c = #status#
/Axel
-Ursprüngliche Nachricht-
Von: Hemant.Kamatgi [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 30. Januar 2008 06:52
An: user-java@ibatis.apache.org
Betreff: Problem with dynamic sql
Hi All,
I'
33 matches
Mail list logo
