Hi,
With reference to this unanswered post

http://forum.hibernate.org/viewtopic.ph ... ht=xmltype

I have a class where one member is mapped by a UserType to the Oracle XMLType


During object creation hibernate makes this insert statement


The insert fails (as does update) with something like "expecting NUMBER got LONG"
If I step through and replace the third ? with xmltype(?) then I can happily insert and update XMLTypes all day long.

My question is :
Is there existing functionality allowing me to set a value in XMLTypeUserType which tells hibernate a custom value to use in place of ?, by calling

instead of


If not I was going to hack hibernate 2.8 to do what I want.
From what I've seen this means making changes to the generateXXXString methods in both net.sf.hibernate.persister.EntityPersister and net.sf.hibernate.persister.NormalizedEntitypersister. Is there anything else I need to be aware of?

I couldn't find anything like this in hibernate 3.0 either (although I may have just not seen it), and it looks like it won't be as easy anyway because the equivalent generateXXXString methods are in the BasicEntityPersister super class, so they have no visibility of the column types.

Is this the kind of configuration that Hibernate should be expected to support, or is it something that is only necessary because of rare vendor specific extensions like XMLType?

Cheers

Simon

In Hibernate3, use <sql-insert> and <sql-update>. See the manual.

Hi Gavin,
Thanks for the amazingly quick reply, thats just was I was looking for :) Sorry i didn't RTM...

Because 3 is in Beta I'd still need to do this in 2.8 initially - will updating the two EntityPersister classes be enough, or do I need to change more?
It would be a very specific modification for XMLType only.

Cheers

Simon

Nah, should be easy enough to override the SQL generation methods in a custom persister.

Yeah I'd seen that but I thought it meant I'd need to write a custom persister for each class that used a field mapped to XMLType (with the associated changes required whenever I updated the class).. so through laziness I was hoping there was a better way, even if it meant changing hibernate :)

If you wanted to add functionality to generate valid sql statements specifically for creating and updating classes with a member mapped to XMLType, for use in 1..n different classes in Hibernate 2.8, how would you do it? Bearing in mind its a filler until we can move to 3 - custom persisters or a change to Hibernate?

Cheers


Simon