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.

Sign up for GitHub

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

Jump to bottom

lastUpdate timestamp should live in the database #45

Open
seanf opened this issue Oct 24, 2014 · 0 comments
Open

lastUpdate timestamp should live in the database #45

seanf opened this issue Oct 24, 2014 · 0 comments
Assignees
@abn
Labels
enhancement
Milestone
1.4.0

Comments

@seanf
Copy link
Contributor

seanf commented Oct 24, 2014

It's an attribute of the database, wherever it lives. For instance, when multiple victims clients are connecting to the same database from different machines, there's no need for them to update the database separately.

Or if the same client is run more than once, but pointing at different databases each time, both databases should be kept up to date, so they shouldn't share a single lastUpdate timestamp.
@abn abn self-assigned this Oct 24, 2014
@abn abn added this to the 1.4.0 milestone Oct 24, 2014
abn added a commit to abn/victims-lib-java that referenced this issue Oct 26, 2014
@abn
Refactor hibernate orm usage
cd6e810 
- VictimsHibernate is now used as a utility class
- VictimsDatabase now contains database interaction specifics
- [Issue victims#45] LastUpdate is now in-database
- Move to in database cache
- Update VictimsResultCacheTest to test in database caching
- Updated models
- Misc. code refactor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@abn abn

Labels
enhancement
Projects
None yet
Milestone
1.4.0
Development

No branches or pull requests
2 participants
@seanf @abn