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

NotificationEventSignal Model Extensions #607

Closed
2 tasks
cdparra opened this issue Sep 2, 2017 · 0 comments
Closed
2 tasks

NotificationEventSignal Model Extensions #607

cdparra opened this issue Sep 2, 2017 · 0 comments
Assignees

Comments

@cdparra
Copy link
Member

cdparra commented Sep 2, 2017

  • Add a OneToMany relationship with User that also contains the boolean attribute read, initialized to FALSE
  • Create the NotificationEventSignalArchive model to periodically archive old signals

Obs: ideally, this model should map to more than one table like notification_event_signals_2017, notification_event_signals_2018 and so forth as we create new archives every certan period of time. One way to do it might be to use @SecondaryTables, so just for future, add a comment on how to use this annotation for future archival tables.

@cdparra cdparra added this to the 201709 Sprint 1 milestone Sep 2, 2017
@cdparra cdparra closed this as completed Sep 6, 2017
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