Have not figured yet how to work it out as a small change without breaking the tests. And I have learned to simulate `vacuumlo` in RDS using SQL, plpgsql, and shell; in the meanwhile. So it's very likely will stick in vanilla 'cas-server-core' until we phase out to CAS 5 endlich, instead. And give up any thoughts on CAS 3 further patching.
Sorry for the noise, > On 24 May 2017, at 18:11, Uxío <[email protected]> wrote: > > Fast note to tell am somewhat working in a small hack branch of CAS Server 3 > core in order to enable tickets' POJOs in JPA mapping under PostgreSQL to be > stored as byteas instead of as oids (i.e. b?lobs). > > Additional tags: cas-server-core, abstractticket, ticketgrantingticket, > serviceticket, hibernate, jdbc, postgres, lob, blob, bytea, aws, ec2, rds, > dms, sct. > > Future-proof following up contact this same handle at the sld outlook tld com. > > Sent from my iPhone -- - CAS gitter chatroom: https://gitter.im/apereo/cas - CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html - CAS documentation website: https://apereo.github.io/cas - CAS project website: https://github.com/apereo/cas --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/458020A7-3554-4AB3-A937-F6D77DF78F24%40madiva.com.
