Commit Graph

10 Commits

Author SHA1 Message Date
NMerz
645cdc90f9 Ready for presentation 2020-12-04 12:25:14 -05:00
Nathan Merz
337372f5f3
Merge pull request #164 from ClaytonWWilson/readmes
Readmes
2020-12-03 22:03:39 -05:00
Nathan Merz
a81eed7946
Spelling fix 2020-12-03 21:06:28 -05:00
Nathan Merz
042679d4a9
Add ItemSearch readme 2020-12-03 21:01:42 -05:00
Adam Ding
9e22d5388d ListItemSearcher tests added 2020-12-01 20:42:50 -05:00
NMerz
3afaad89ea Use plain table search history
This is easier, clearer, faster for inters, and ultimately not really much less space efficient than trying to store this in a serialized nor unreasonably slow for retrievals.

Food for thought: Would this might be well-suited to a nosql database?
2020-11-14 12:05:50 -05:00
NMerz
8653b9a035 Try storing serialized search object
Does not seem to be the best solution (https://stackoverflow.com/questions/17662236/java-write-object-to-mysql-each-field-or-serialized-byte-array)  and does not entirely work, but saving it for posterity because there are some interesting changes here
2020-11-14 11:40:42 -05:00
NMerz
45c7ac15bd Limit item search results
Add a limit on item search results so the user is not overwhelmed.
2020-10-24 11:53:12 -04:00
NMerz
56c9a3f99d Switch to millis for times
There are issues with the serialization of the time objects since the constructors are not public. Passing times around in milliseconds avoid them.
2020-10-06 21:39:23 -04:00
NMerz
68051fdaca Item Search V1
Still needs testing.
2020-10-05 22:54:43 -04:00