Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fk_entity_remarks_remark1 constraint #104

Open
gvdev-git opened this issue Aug 19, 2019 · 2 comments
Open

fk_entity_remarks_remark1 constraint #104

gvdev-git opened this issue Aug 19, 2019 · 2 comments

Comments

@gvdev-git
Copy link

gvdev-git commented Aug 19, 2019

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

@gvdev-git gvdev-git changed the title entity_remarks fk_entity_remarks_remark1 constraint fk_entity_remarks_remark1 constraint Aug 19, 2019
@dhfelix
Copy link
Contributor

dhfelix commented 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.

@gvdev-git
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants