openjpa-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Virag Kothari <vi...@yahoo-inc.com>
Subject Re: byte[] mapped to BLOB and not VARBINARY
Date Wed, 17 Jul 2013 04:17:35 GMT
Thanks for the replies.

Figured that we can set/override in orm.xml something like this:

  <entity class="org.apache.oozie.WorkflowActionBean">
    	<attributes>
    		<basic name="slaXml">
    			<column name = "sla_xml" column-definition="VARBINARY(10000)"/>
    		</basic>
    	</attributes>
    </entity>

--Virag






On 7/16/13 8:29 PM, "Alejandro Abdelnur" <tucu00@gmail.com> wrote:

>but that would require the sql type to be avail in all db servers where
>this is used correct?
>
>how could this be set in the persistence.xml or orm file on per db basis?
>like forcing a dictionary change?
>
>thx
>
>Alejandro
>(phone typing)
>
>On Jul 16, 2013, at 19:36, Ted <r6squeegee@gmail.com> wrote:
>
>> this is what I do
>> 
>> @Column(nullable = false, columnDefinition = "tinyint(1)")
>> 
>> change the tinyint to what ever you want
>> 
>> On 7/17/13, Virag Kothari <virag@yahoo-inc.com> wrote:
>>> Hi All,
>>> 
>>> Is there a annotation which can hint the mapping from byte[] to
>>>VARBINARY?
>>> I have the following defined but the column gets mapped to a BLOB and
>>>not
>>> VARBINARY. This is happening for Oracle.
>>> 
>>>    @Basic
>>> 
>>>    @Column(name = "foo")
>>> 
>>>    private byte[] foo = null;
>>> 
>>> 
>>> Thanks,
>>> 
>>> Virag
>> 
>> 
>> -- 
>> Ted.


Mime
View raw message