[hibernate-issues] [JIRA] (BVAL-755) Allow activation typedef depending on flags/dialect

[Enrique Gonzalez Martinez (JIRA)]

Enrique Gonzalez Martinez ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A0f7f2bdc-c37c-4182-8f39-c2feb9cf2596 ) *created* an issue

Bean Validation ( https://hibernate.atlassian.net/browse/BVAL?atlOrigin=eyJpIjoiNzllYjAyMjA2NTBlNDM2Nzk4MmVkMTkwZjBlNzdiN2MiLCJwIjoiaiJ9 ) / Improvement ( https://hibernate.atlassian.net/browse/BVAL-755?atlOrigin=eyJpIjoiNzllYjAyMjA2NTBlNDM2Nzk4MmVkMTkwZjBlNzdiN2MiLCJwIjoiaiJ9 ) BVAL-755 ( https://hibernate.atlassian.net/browse/BVAL-755?atlOrigin=eyJpIjoiNzllYjAyMjA2NTBlNDM2Nzk4MmVkMTkwZjBlNzdiN2MiLCJwIjoiaiJ9 ) Allow activation typedef depending on flags/dialect ( https://hibernate.atlassian.net/browse/BVAL-755?atlOrigin=eyJpIjoiNzllYjAyMjA2NTBlNDM2Nzk4MmVkMTkwZjBlNzdiN2MiLCJwIjoiaiJ9 )

Issue Type: Improvement Assignee: Unassigned Created: 25/Jun/2020 04:05 AM Priority: Major Reporter: Enrique Gonzalez Martinez ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A0f7f2bdc-c37c-4182-8f39-c2feb9cf2596 )

Currently jBPM/RHPAM supports databases provided by hibernate orm. Currently we are facing problems with just one of the dialects: postgreSQL.
At present this dialects supports oid which is a problem in certain enviornments like AWS, also some users are reluctant to use this as blob to store some of the data we use at jBPM.

While the use of @typedef could fix our problem AFAIK this would affect all dialects and I could not find a way to restrict or activate only under certains flags (var env) or circunstances (e.g. certain dialect)

It would be perfect to be able to set some sort of condition when some typedef applies. if that is not possible I would like to know if there is a workaround to provide a way programatically or not to set a type def.

This would allow us to migrate to a new schema based on bytea instead of oid eventually to all users.

After dicussion we are trying to avoid the subclassing of the dialect as it would tied the user to a jbpm solution and not really a OOTB solution provided by hibernate team.

Keep in mind that we use hibernate through JPA spec.

( https://hibernate.atlassian.net/browse/BVAL-755#add-comment?atlOrigin=eyJpIjoiNzllYjAyMjA2NTBlNDM2Nzk4MmVkMTkwZjBlNzdiN2MiLCJwIjoiaiJ9 ) Add Comment ( https://hibernate.atlassian.net/browse/BVAL-755#add-comment?atlOrigin=eyJpIjoiNzllYjAyMjA2NTBlNDM2Nzk4MmVkMTkwZjBlNzdiN2MiLCJwIjoiaiJ9 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100130- sha1:74b7c6b )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hibernate-issues/attachments/20200625/f084792c/attachment.html