You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The default SQL schema has the following constraint for entity_remarks:
CONSTRAINT 'fk_entity_remarks_remark1'
FOREIGN KEY ('rem_id')
REFERENCES 'rdap'.'remark' ('rem_id')
ON DELETE NO ACTION
ON UPDATE NO ACTION)`
Due to this entity remarks can be used only once. I doubt that this is the intended behaviour, at least dropping the constraint allows to re-use remarks just fine. IMHO the constraint should be dropped or extended to ent_id
The text was updated successfully, but these errors were encountered:
gvdev-git
changed the title
entity_remarks fk_entity_remarks_remark1 constraint
fk_entity_remarks_remark1 constraint
Aug 19, 2019
As far as I know the unique index is the reason that you can use only one remark per entity.
UNIQUE INDEX `rem_id_UNIQUE` (`rem_id` ASC)
Remark are intended to provide remarks on a particular entity.
If you want to create notices for all the entities, you can use this guide to create notices https://www.reddog.mx/notices.html, or as a last resource drop the unique index.
let me know if this works for you, or if I misunderstood your message.
Thanks for the quickl response! The intention was to add a custom message to registrant handles of domains that are for sale, i.e. basically the same remark used in different places. This seems to work without the constraint. If that is not compatible with your future plans we'll need to think of something else
The default SQL schema has the following constraint for entity_remarks:
Due to this entity remarks can be used only once. I doubt that this is the intended behaviour, at least dropping the constraint allows to re-use remarks just fine. IMHO the constraint should be dropped or extended to
ent_id
The text was updated successfully, but these errors were encountered: