You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #485, we come to couple of issues, which were not solved:
id fields are now bigint(20), were int(11). Nevertheless, bigint is typically not needed, there won't be more than 2.1 billions of records. This happens for most of the attributes which are PK/FK. Solution: PK/FK should be just ints. Problems: It was not possible to force JPA to generate ints and at the same time having id attributes as Long.\
name in ppl_model is correctly varchar(1024), but there is no UNIQUE index, because it cannot be created automatically by JPA. The cause: In the mysql script, we added the index as follows:
-- This constraint is only limited to first 255 characters in column. Larger constraint is only
-- possible with 'innodb_large_prefix' setting on database.
ALTER TABLE ppl_model ADD UNIQUE (name(255));
Goal: Finalize the issues above
The text was updated successfully, but these errors were encountered:
In #485, we come to couple of issues, which were not solved:
Goal: Finalize the issues above
The text was updated successfully, but these errors were encountered: