Finally to attempting to run the migrated app - WHY is it generating dozens of dropIndex changeset entries?

Support
#1

So finally, I’m on step 12 of the migration and about to run the migrated app for the first time.

But… there’s dozens of dropIndex changeset entries - why!?!?!?! These indexes are 100% needed to drive quick lookups; why in the world would Jmix want to drop them!?!?!

image

#3

Add the indexes to entity definitions like that:

@JmixEntity
@Table(name = "CITY", indexes = {
        @Index(name = "IDX_CITY_COUNTRY_ID", columnList = "COUNTRY_ID")
})
@Entity
public class City {