Restricting timestamps in Kea backends to max supported values
The following chapter of the Kea User's Guide Limitations Related to the use of SQL Databases claims that we restricted timestamps to 32 bit value past the epoch. I don't see us restricting this anywhere. Maybe we should revise which databases have which limitation and explicitly report an error upon an attempt to add higher timestamps.
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information