From class org.opensaml.storage.impl.JPAStorageRecord:
@Lob @Column(name="value", nullable = false) @Nonnull @Override public String getValue()
The @Lob apparently causes Hibernate, when used together with Postgresql, to use the "value" column to store a large object's OID as a string, but this value is not seen as an object reference by Postgresql so the large object is immediately orphaned (vacuumlo would delete it). Overriding the @Lob annotation with a custom orm.xml mapping makes Hibernate store the actual value (JSON) in the column, as it probably should. Would it be possible to remove @Lob in order to get correct behaviour with Postgresql? I don't know how this would affect other database engines...
Environment
IdP 3.1.2
Postgresql 9.2 or 9.4, with corresponding JDBC connector
Activity
Show:
Daniel FisherOctober 9, 2018 at 4:40 AM
Updated shib wiki.
Brent PutmanSeptember 21, 2018 at 4:18 PM
Discussed on call today. Daniel will look at and confirm final status of docs etc for 3.4.0.
From class
org.opensaml.storage.impl.JPAStorageRecord:The
@Lobapparently causes Hibernate, when used together with Postgresql, to use the "value" column to store a large object's OID as a string, but this value is not seen as an object reference by Postgresql so the large object is immediately orphaned (vacuumlowould delete it).Overriding the
@Lobannotation with a custom orm.xml mapping makes Hibernate store the actual value (JSON) in the column, as it probably should. Would it be possible to remove@Lobin order to get correct behaviour with Postgresql? I don't know how this would affect other database engines...