[odb-users] Unique index in abstract class

Boris Kolpackov boris at codesynthesis.com
Thu Oct 1 11:40:35 EDT 2020

Патрушев Данил Андреевич <d.patrushev at prosoftsystems.ru> writes:

> Second, I don't see how there can be a table name conflict. I am going
> to present an example, please, excuse me for stating obvious things,
> just want to be absolutely clear.

No problem, precision is always appreciated.

> Say "A" is an abstract class, "B" inherits "A" and is concrete, "C"
> inherits "A" and is concrete. ODB generates two tables named "B" and
> "C", correct?  Now,  we would like to apply a unique index to a field
> in "A", which is shared. The first thing to try is to add
> #pragma db index unique member(m_field)
> in "A". That gives us index "A_field_i" in the definition of "B" and
> index "A_field_i" in the definition of "C" -  same name. The table
> names are still different, why shouldn't they? I suppose it is the
> scope of the index definition, namely, class "A" that drives the
> choice of the index name.

Yes, this is a bug in ODB.

> We worked around the issue by writing
> #pragma db index unique member(m_field)
> in the body of "B" (we reference m_field which is defined in "A") and
> the same pragma in the body of "C". That gave us "B_field_i" in "B"
> definition and "C_field_i" in "C" definition.

Yes, those "B_" and "C_" prefixes in the index names are the table names
of B and C.

> I don't know if this is legal but this approach used to work for us
> for some time, but it no longer does.

Yes, this is a good workaround (and that's essentially what ODB would
do once we fix the bug). What is not clear is the "no longer works"
part: the only way I see this happenning is if your table names were

> Considering what I've tried to get across, do you still recommend
> the mechanisms you mentioned in your reply?

That depends on the reason why your workaround no longer works.

More information about the odb-users mailing list