In the edit user popin, we show the last visit date and time. This date is taken from the history table, which leads to 2 problems:
if the table gets big (which is often a problem, as long as we have not implemented #370 ) the SQL query to get the last visit can take very long (several seconds)
if the history is disabled, we show an incorrect information
To avoid these problems, we can simply register the date and time in a new column users.last_visit
In the edit user popin, we show the last visit date and time. This date is taken from the history table, which leads to 2 problems:
1) if the table gets big (which is often a problem, as long as we have not implemented #370 ) the SQL query to get the last visit can take very long (several seconds)
2) if the history is disabled, we show an incorrect information
To avoid these problems, we can simply register the date and time in a new column users.last_visit
<!-- github-sync-id:153967047 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
In the edit user popin, we show the last visit date and time. This date is taken from the history table, which leads to 2 problems:
if the table gets big (which is often a problem, as long as we have not implemented #370 ) the SQL query to get the last visit can take very long (several seconds)
if the history is disabled, we show an incorrect information
To avoid these problems, we can simply register the date and time in a new column users.last_visit