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

nharker-core: split up core and nitrite #224

Open
tsbonev opened this issue Feb 14, 2019 · 0 comments
Open

nharker-core: split up core and nitrite #224

tsbonev opened this issue Feb 14, 2019 · 0 comments
Assignees
Labels
bug Something isn't working domain Make a domain decision
Projects

Comments

@tsbonev
Copy link
Owner

tsbonev commented Feb 14, 2019

Currently the core domain objects have references to Nitrite due to their indexing. It might be beneficial to split up the domain objects into pure POJOs and have adapted Nitrite objects that hold their index information.
This might aid searching (see #222) as the Nitrite object that is persisted won't clutter the domain with its extra DB-related fields.
Also this will allow deletion to be migrated to a 'deletedOn' field instead of a separate generic table (see #223).

@tsbonev tsbonev added the domain Make a domain decision label Feb 14, 2019
@tsbonev tsbonev self-assigned this Feb 14, 2019
@tsbonev tsbonev added this to To Do in NHarker 0.2 via automation Feb 14, 2019
@tsbonev tsbonev added the fix This fixes a bug or mistake label Feb 19, 2019
@tsbonev tsbonev changed the title nharker-core: consider splitting up core and nitrite nharker-core: split up core and nitrite Feb 19, 2019
@tsbonev tsbonev added bug Something isn't working and removed fix This fixes a bug or mistake labels Feb 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working domain Make a domain decision
Projects
NHarker 0.2
  
To Do
Development

No branches or pull requests

1 participant