There is no way to do this.
You always need a primary key on a table when you
want to define a replicate on it, regardless if you
setup an update anywhere or a master-slave replication.
Also be careful if you currently have a unique index and
want to 'upgrade' this to a primary key in order to use
ER.
Your application might fail, because they receive different
error message during an insert of a duplicate key
in this table.
- table with unique index
-> -239 'could not insert new row - duplicate value....'
- table with primary key constraint
-> -268 'unique constraint violated'