08-23-2018, 12:58 PM
Really interesting; I hadn't even considered a cron job.
My thoughts had been going along the lines of calculating a concatenation of the year + month + day + increment starting at 100 which would happen when the DB record is created. But 'm not sure that's even possible.
It wouldn't really matter about resetting the trailing number as I doubt we'd ever get more than 150 registering on the same day, so the date prefix would guarantee the uniqueness. Part of my logic is that it would be easy to work out when their subscription is due even if you were nowhere near a computer (e.g. at the annual conference).
As a corollary question, how easy would it be to replace the dependence on the username in the out-of-the-box version? It seems like you can't do anything without creating it.
My thoughts had been going along the lines of calculating a concatenation of the year + month + day + increment starting at 100 which would happen when the DB record is created. But 'm not sure that's even possible.
It wouldn't really matter about resetting the trailing number as I doubt we'd ever get more than 150 registering on the same day, so the date prefix would guarantee the uniqueness. Part of my logic is that it would be easy to work out when their subscription is due even if you were nowhere near a computer (e.g. at the annual conference).
As a corollary question, how easy would it be to replace the dependence on the username in the out-of-the-box version? It seems like you can't do anything without creating it.