During development of ER diagram I found that varbinay type is mapped to longvarbinary in case of HSQLDB DBMS. The result is:
create table TEST (ID bigint generated by default as identity (start with 1), IP_ADDRESS longvarbinary(16), primary key (ID));
This is wrong format for HSQLDB and it is resulted in: “Unexpected token in statement [create table…]”
I’ve pass this issue to our engineers to investigate and will get back to you shortly.
I would like to let you know the fix for longvarbinary problem has been fixed and please find the patch build at the following link. If you need any help, please let me know!