Deprecate parent composite primary keys - leave management via table index

Added IsKey to table index to define that index being created is a primary key.

Table index is creating unique key and postgresql REQUIRES a primary key to work.

Translation tables are not working with error:
org.postgresql.util.PSQLException: No primary key found for table C_CountryGroup_Trl.

Discovered at workshop Burg 2014.

Hi Carlos,

I agree, your solution makes sense.

+1 for me !

Regards,

Nicolas

Hi @Nicolas Micoud,

I think the creation of the composite primary key is not consistent in the app.

• if you use packin to create a new table with composite key - then the primary key is not created

• if you create a table with a few columns not parent and push synchronize - the primary key is not created

• if you push the synchronize column with all the parent columns created - the primary key is created

• if you push the synchronize column with some of the parent columns created - the primary key is created wrongly and it can't be fixed later in the app

In other words - composite primary key is being created on MTable.getSQLCreate, and that's just called if the table does not exist and is useful just if all the parent columns are already defined - otherwise it can create a problem.

So, my vote would be to drop that code that creates composite primary keys and move the management of those keys exclusively to table index.

WDYT?

Regards,

Carlos Ruiz