[MySQL] Database timestamps reset upon using RP date & time.

[windowswill]

When adding records to the accounts table in the UFGQ database, I used the RP dates (2412 instead of 2012) to input dates for induction and promotion. Once set, they promptly reset to all zeros, forcing me to use real time dates.

[Morketh]

Database currently uses the Unix Time stamps for any date/time. Currently Unix time stamps are only 32 bit and as such they only go up to January 19, 2038 03:14:08 GMT. I will look into building a better and more flexible way of handling arbitrary dates/times.

[Morketh]

• Right now it’s 13:30 EST, November 2, 1996 (which means it is 18:30 GMT). The last leap year, not including this one, was 1992. That’s 92 years of century passed as of January 1, 1992. That’s also 92 × 365.25 = 33603 days. Call this A.
• Since then, there have been the full years 1992–1995. This is 366 + 365 + 365 + 365 days, or 1461 days. Call this B.
• Since January 1, 1996, there have been 31 + 29 + 31 + 30 + 31 + 30 + 31 + 31 + 30 + 31 days completed as of the end of October 31. This is 305 days. Call this C.
• This month, there has been 1 complete day (November 1). Call this D.
• As of this time, about 0.77 days have passed today (I keep more significant digits when using the program). Call this E.
• 100 years is equal to 36,525 days. Call this F.
• Calculate the stardate fraction: (A + B + C + D + E) ÷ F = 0.9683989…
• To put this into the format used in Star Trek: The Next Generation, simply multiply by 100,000. Truncating (never round; you have to complete a time unit before you count it), this gives you stardate 96839.8. The benefit of doing it this way is its a floating point number that can be easily transfered between SL and PHP also either the PHP script or the LSL script can calculate the time. and the database will no longer complain about the values or reset them to ZERO.