redundant index e_er for table servoy_element

Classic Servoy
1

warning in v3.1, redundant index “e_er” for table “servoy_element”, in the repository

This appears to be an index of the composite primary key

2

index e_er covers element_id and revision, the pk covers element_id, uuid and revision, in that order.
A query on element_id and revision only and not the uuid is not covered by the pk index, that’s why we need the e_er index.

Rob

3

my repository was v2.6, updated to v3.0, so it may be different

unload shows this:
TABLE “DBA”.“servoy_elements”
(
“element_id” integer NOT NULL ,
“revision” integer NOT NULL ,
“parent_element_id” integer NULL ,
“object_type_id” integer NOT NULL ,
“root_element_id” integer NULL ,
“uuid” varchar(37) NULL ,
PRIMARY KEY (“element_id”, “revision”),
)

thanks,
greg

4

Greg,

There is a small difference between a fresh v3 repository and an upgraded v2 repository.
In v2 servoy_elements has the pk as you listed.
In v3 the pk of servoy elements is extended with uuid and a new index unique e_er is created covering the old pk columns.
In the upgrade process, however, the pk is not extended resulting in a duplicate index.

This is not causing any problems and if you want to get rid of this message you can create a new v3 repository and import your solutions into the new one.

Rob

5

I am new to servoy, and find this frustrating

we are told to copy the v2 repository, the v3 installer says “repository updated”, but it’s not really updated. It’s different

now, when you see a “bug”, you have to ask if this was upgraded, or a fresh install. Just like FileMaker v7! :slight_smile:

please, please, post proper instructions for upgrading on your web site. I only see info posted here in the forum

thanks
greg

6

Greg,

In next major Servoy release the servoy_elements table will be corrected in the repository upgrade and will be the same as in a fresh repository.

Rob