ias,
PathInfo aPathInfo)
and then you can give the field descriptor to myAppendParameter and from
there to asDBParameter and in this function you can perform your strategie.
Hope that helps,
CL
-Original Message-----
From: Janssen, Roger [mailto:[EMAIL PROTECTED]
Sent: Donnerstag, 08. Mai 2008
08 5:04 PM
To: 'OJB Users List'
Subject: RE: Is it possible to force OJB not use execute a prepared
statement?
Hi Roger, sorry for my delay.
> As I understand your example, it boils down to the appendParameter
> method
in your solution.
> That method adds the String represe
chance that I got it completely wrong, please
let me know.
Greetings,
Roger Janssen
iBanx
-Original Message-
From: Christian Lipp [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 05, 2008 5:45 PM
To: 'OJB Users List'
Subject: RE: Is it possible to force OJB not use execute a pre
wrong, please
let me know.
Greetings,
Roger Janssen
iBanx
-Original Message-
From: Christian Lipp [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 05, 2008 5:45 PM
To: 'OJB Users List'
Subject: RE: Is it possible to force OJB not use execute a prepared statement?
In the OJB pr
}
You have to build your own strategie. I will post our strategies soon.
Greetings, CL
-Original Message-
From: Janssen, Roger [mailto:[EMAIL PROTECTED]
Sent: Mittwoch, 05. März 2008 15:02
To: OJB Users List
Subject: RE: Is it possible to force OJB not use execute a prepared
stat
Hi Christian,
The problem, I believe, is with the number of parameters (parameter
markers) that crosses a certain boundary. We ran into an upper limit of
2000 (or something like that) on MSSQL server. That is a problem for us
because we sometimes generate queries that have more parameters (yes...
here on the mailing list
(we are using db2 and could increase the performance 40% in online acces and
50% in batch access).
CL
-Original Message-
From: Armin Waibel [mailto:[EMAIL PROTECTED]
Sent: Montag, 03. März 2008 16:19
To: OJB Users List
Subject: Re: Is it possible to force OJB not
Hi Roger,
Janssen, Roger wrote:
Hi,
Just a general question about sql statement execution.
Is it possible to force OJB not to execute a prepared statement, but to
execute the sql as a regular sql statement?
Sorry no! The use of prepared statements is deeply rooted in the OJB core.
The
