On Tue 05 Oct 2010 14:06 +0200, Lukas Fleischer wrote: > On Sun, Oct 03, 2010 at 01:35:45PM -0500, Dan McGee wrote: > > On Sun, Oct 3, 2010 at 1:34 PM, Lukas Fleischer > > <archli...@cryptocrack.de> wrote: > > > I basically agree and I already changed the patch to only the > > > "OutOfDateTS" column only. The only thing that I'm not sure how to > > > implement is the migration code, notably the default timestamp to use > > > for packages that are flagged out-of-date when upgrading. > > > > > > Which is the best value to choose? Zero? UNIX_TIMESTAMP()? > > > > Current time is probably the best idea. I also have no idea why this > > isn't just a datetime column. > > It isn't a DATETIME cause I just copy/pasted the "ModifiedTS" column. > > Loui, is there any reason for using BIGINTs instead of DATETIMEs for > timestamps?
Not that I know of. It's a legacy of whoever designed the database in the beginning. Generally I haven't touched anything that works because I'm still learning PHP and SQL as needed to fix bugs.
