I don't have the answer, because I haven't had the issue,
but would it be possible to use token replacement like clinton described
last week?
I have no idea of you can replace the tokens runtime for the session
though...
select id=findOrders parameterClass=org.test.OrderSearchCriteria
Hi!
In our DB schema (that cannot be changed) we got dynamic table names, depending
on the current company, i.e. there are tables ORDER_100, ORDER_200,... with
ORDER_100 being company 100's ORDER table, etc.
Now everything is fine, for a single select, as I can pass the current company
as a
HiI have configured my data Source as below
transactionManager type=JDBC
dataSource type=SIMPLE
property name=JDBC.Driver value=com.ibm.as400.access.AS400JDBCDriver /
property name=JDBC.ConnectionURL
value=jdbc:as400:MYAS400/MYDB;naming=system;date format=iso;time
format=hms;prompt=false /
Not that I am throwing stones, but you really should raise an issue about
this schema design. I perviously worked in a company that took this
approach in designing their data model. As you have already seen, this is
not an easy data model to work with for obvious reasons, but the greatest
I am trying to mold my code so it works with oracle stored procedures. The
SP will return multiple resultsets (cursors) and will also take in a
parameter.
I was looking at the following example on the wiki.
http://opensource.atlassian.com/confluence/oss/pages/viewpage.action?pageId=5653
I have
As far as I know, U cant do multiple cursor returns with Ibatis. I remember
having tried it way before and was unsuccessful. Am not sure if the later
versions have them.
-Sundar
On Mon, May 4, 2009 at 12:33 PM, Bhaarat Sharma bhaara...@gmail.com wrote:
I am trying to mold my code so it works
Could you paste parameterMap definition ?
2009/5/4 Bhaarat Sharma bhaara...@gmail.com:
I am trying to mold my code so it works with oracle stored procedures. The
SP will return multiple resultsets (cursors) and will also take in a
parameter.
I was looking at the following example on the
Neither would I throw stones at anyone, but remember that dynamic table
identifiers can be an issue on some RDMS (for instance; Oracle table names
cannot exceed 30 characters).
This problem can easily be avoided with validation code, but in your case, I
would strongly advocate using the DBMS