Hi!
I've looked into what is missing to make me complete the basic callable statement support in collectionpersisters and basically
the current "biggest" challenge is that it requires a change in CollectionPersister interface.
What is needed is simply the possibility to "overule" at what position writeElement, writeKey and writeIndex starts from.
Today they always assume 1+(writeorder and otherstuff), now they need offset+(writeorder and otherstuff).
This is necessary as we need to do something like:
callstatement.registerOutParameter(1 Types.NUMERIC); to allow storedprocedures to return a result (which currently is simply "number of rows updated").
So, can you seen any problems in breaking/changing the CollectionPersister interface in v22branch ?
Best regards, Max
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
hibernate-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
