ERROR: org.hibernate.engine.jdbc.spi.SqlExceptionHelper Bad value for type long

Submitted by mateusz.grajper... on Tue, 05/12/2020 - 15:22

Hello.

First of all I am new into Bonita so sorry for any mistakes in describing a problem.
I have a project using Bonita with postgres. I created a table that contained several columns - some was string (character varying 255), some was text. After few days it happened that one string column must been extended to text size. When I changed my bom.xml file and deployed it Bonita does not altered a table so I made it manually. Now there is no problem with inserting any value, but when reading data I have an exception:

2020-05-07T11:21:40+00:00 172.29.0.1 bpm[59753]: 2020-05-07 11:21:40.710 +0200 WARN: org.hibernate.engine.jdbc.spi.SqlExceptionHelper SQL Error: 0, SQLState: 22003
2020-05-07T11:21:40+00:00 172.29.0.1 bpm[59753]: 2020-05-07 11:21:40.710 +0200 ERROR: org.hibernate.engine.jdbc.spi.SqlExceptionHelper Bad value for type long : Some not numeric input

I have heard, that it sometimes require to mark a @Lob column to be text, but I don't know if it is possible in Bonita. Does anybody know a solution to this kind of problem?

My set is:
Bonita Studio version 7.9.2
PostgreSQL 11.2, 64-bit
Red Hat 4.8.5-36

Best regards,
Mateusz

#postgresql

Log in or register to post comments
5082 reads

1 answer

Submitted by Pablo Alonso de... on Tue, 05/12/2020 - 17:04

Hi Mateusz,

If I am not wrong, what you have done is to change an attribute of a BDM object from String to Text.

This implies a change of column type not only the size of the column. Have in mind that doing that kind of changes in any database can generate a data lost.

My recomendation is to create a new column Text (to see the exact format, do a dummy object with same conf and deploy it), migrate from old column to new one, remove old column, and rename new one into old name.

Cheers

Log in or register to post comments
399 reads

Comments

Submitted by mateusz.grajper... on Wed, 05/13/2020 - 09:22

Thank you for the reply but it didn't resolve my problem. I just skipped describing altering procedure as I thought that is not a case here - type of column was changed correctly, inserting and selecting through SQL works fine, no data loss. Just in case I did it again but still nothing changed: SQL everything works fine and type was changed, Bonita can insert but produces mentioned exception while reading non-numeric record.

Permalink