|
|
|
|
|
|
When AG used parameter with length longer than 4000 ... for example in table INSTALLATION and parameter DEVICETOKEN ... table IOSVARIANT and parameter CERT_DATA (master branch).. it becomes problem because oracle has Varchar2 with max length 4000 and when parameter is longer it needs LOB ...
Changed in table INSTALLATION parameter DEVICETOKEN as VARCHAR2(4000) ... it is temporary solution .. but in IOSVARIANT parameter CERT_DATA has length 100000 and it is too large. In version 1.0.x certificate was LOB and it was ok for oracle.
Object with large length as CERT_DATA makes it impossible to support oracle.
Postgres bug that probably lead to the change of implementation:
https://issues.jboss.org/browse/AGPUSH-1144
EDIT:
If change orm.xml (in unifiedpush-model-jpa/src/main/resources/META-INF)
FROM
.
.
.
<entity class="iOSVariant" access="FIELD">
<discriminator-value>ios</discriminator-value>
<attributes>
<basic name="certificateData">
<column name="cert_data" length="100000"/>
</basic>
</attributes>
</entity>
.
.
.
TO:
.
.
.
<entity class="iOSVariant" access="FIELD">
<discriminator-value>ios</discriminator-value>
<attributes>
<basic name="certificateData">
<column name="cert_data"/>
<lob/>
</basic>
</attributes>
</entity>
.
.
.
In oracle, parameter "private String certificateData;" was represent as CLOB ... and AG works correctly. In version where was certificate as byte[] it was represent as BLOB.
... but in Postgres it is probably problem (same as https://issues.jboss.org/browse/AGPUSH-1144)
|
|
|
|
|
|
