Home » Support » Forum » Indexes broken after schema update.

Indexes broken after schema update.

#1

Anyone else noticed this?

I updated an entity Object with some new fields, restarted the database to pick up the new schema and now none of the indexes work, except the @Id.

I can query by any field that is not indexed on the existing Object but as soon as I try and query against a field that was indexed I get no results.

Tried 2.4.2 and 2.4.2_02 with same results.

#2

Adding new persistent fields should not affect indexes and queries, as long as you restart the database server before using the revised schema.

It is a common operation to add persistent fields to existing applications, and currently there are no related open issues, so if you still have this problem after restarting the database server - please provide more details.

ObjectDB Support
ObjectDB - Fast Object Database for Java (JPA/JDO)

Post Reply

To post a reply and/or subscribe to update notifications - please login