Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backoffice doesn't work for postgres with fields of type char #158

Open
FroMage opened this issue Aug 31, 2023 · 0 comments
Open

Backoffice doesn't work for postgres with fields of type char #158

FroMage opened this issue Aug 31, 2023 · 0 comments

Comments

@FroMage
Copy link
Contributor

FroMage commented Aug 31, 2023

Apparently, postgres disallows char fields with a 0 (default) value, resulting in interesting issues like:

	Suppressed: org.hibernate.exception.DataException: could not execute statement [ERROR: invalid byte sequence for encoding "UTF8": 0x00
  Where: unnamed portal parameter $19] [insert into ExampleEntity (arrayBlob,date,enumeration,lobString,localDate,localDateTime,somethingLocalTime,longString1,longString2,longString3,longString4,manyToOne_id,contents,mimeType,name,oneToOneOwning_id,primitiveBoolean,primitiveByte,primitiveChar,primitiveDouble,primitiveFloat,primitiveInt,primitiveLong,primitiveShort,requiredString,sqlBlob,string,wrapperBoolean,wrapperInt,id) values (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)]

Not sure what value to attach to a char under those circumstances.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant