Abstract: Disclosed herein are various approaches for supporting active-active replication in a blockchain table having a primary key constraint. A blockchain database object may be stored in a first database, the blockchain database object comprising a field defined as a primary key for the database object and a visibility field. A first row may be inserted in the database object, the first row comprising a particular value for the field designated as the primary key. A primary key value conflict may be detected between the first row and a second row from a second database, the second row comprising the particular value for the field defined as the primary key. A conflict resolution procedure may be implemented to determine that the first row is a winning row of the primary key value conflict between the first row and the second row. A visibility field may be stored within the second row to indicate that the second row does not represent a valid row with respect to the primary key.

Abstract: Disclosed herein are various approaches for supporting active-active replication in a blockchain table having a primary key constraint. A blockchain database object may be stored in a first database, the blockchain database object comprising a field defined as a primary key for the database object and a visibility field. A first row may be inserted in the database object, the first row comprising a particular value for the field designated as the primary key. A primary key value conflict may be detected between the first row and a second row from a second database, the second row comprising the particular value for the field defined as the primary key. A conflict resolution procedure may be implemented to determine that the first row is a winning row of the primary key value conflict between the first row and the second row. A visibility field may be stored within the second row to indicate that the second row does not represent a valid row with respect to the primary key.