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
..
Chain/src	Add chainID to Chain class Lambda	2020-11-01 21:08:07 -05:00
Item	Merge branch 'master' into APIUnitTests	2020-10-08 19:10:16 -04:00
ItemSearch/src	Use plain table search history	2020-11-14 12:05:50 -05:00
List	Login updates	2020-11-06 12:51:34 -05:00
ListEntry	Merge identical ListEntries	2020-10-09 00:11:44 -04:00
ListShare	Update lambda tests	2020-11-01 12:46:03 -05:00
SearchHistory/src	Use plain table search history	2020-11-14 12:05:50 -05:00
src	Update StatementInjector for missing rsReturns	2020-10-09 00:15:57 -04:00
target	Add Core Lambda Unit tests	2020-10-07 00:04:17 -04:00
User	Send more detailed account deletion email	2020-11-04 22:08:34 -05:00
pom.xml	Try storing serialized search object	2020-11-14 11:40:42 -05:00