The current system uses MySQL autoincrement (sequential number) fields. These are not shown to the user except in the Visits index page. Note that the page lists the most recent record first, with the highest sequential number.
Experiments show that moving to MongoDB would be straightforward, except that Mongo generates unique _ids as cryptic object identifiers, not sequential numbers.
Reimplement existing behavior in a way that is expected to work with Mongo as well as MySQL:
[x] Modify the Visits index page so that the sequential number shown in the first column is no longer coming from the database record; instead, it is generated in the server-side EJS. Notice that the numbers should be descending.
The current system uses MySQL autoincrement (sequential number) fields. These are not shown to the user except in the Visits index page. Note that the page lists the most recent record first, with the highest sequential number.
Experiments show that moving to MongoDB would be straightforward, except that Mongo generates unique
_ids as cryptic object identifiers, not sequential numbers.Reimplement existing behavior in a way that is expected to work with Mongo as well as MySQL: