Recently Viewed: move list to server side

[davidwatkins73]

Currently the recently viewed list is persisted in the browsers LocalStorage. This occasionally causes problem when users change browsers/machines. Look to store this list in user prefs instead.

[davidwatkins73]

Option 1:

• increase size of user_preference/value table/col
  • currently it's 2048 chars, however history can exceed this (slightly) when visiting pages with big names.

Option 2:

• leave user_preference table at 2048 chars, but use truncateMiddle(....) to ensure the names aren't too big
• this has the benefit of making the drop down nicer (which could be done anyway by calling it at render time)

Option 3:

• see if we can re-use access_log table. However it could be painful to parse and get entity types/names from the data held in there e.g.

  with history as (
  select * from access_log
  where user_id = 'david.watkins@db.com'
  and state not like '%|%'
  order by created_at desc
  offset 0 rows
  FETCH NEXT 100 ROWS ONLY
  )
  select distinct state, params
  from history

Option 4:

All new tables (lots of work!)

[davidwatkins73]

I'd start with Option 1, but consider the worst case scenarios, so we may still need some sort of limiting (perhaps on the server side)