Jerry,
Let SQL return the dates.. it can sort on the dates, and search on the dates.
SELECT * FROM Links Where Add_Date < current_date()
You can also change the date format to almost anything (look in the middle of the mysql book for a good table).
The problem with Timestamp is that it's an auto-update field. Every time the database record is accessed it changes. It's sort of a 'date of last mod' field. That would not be a bad idea for the 'updated' field, except (or because) Admin modifications would be recorded as well as user mods.
I have added a "Time" field to the record, and that is probably the easiest way to do it. That way you can easily sort by time_of_day to see when most activity is, etc.
The time I use is HH:MM:SS and it works just fine through the DBSQL.pm interface with the Links table.
I probably would change the Mod_Date to a timestamp and add a TimeOfDay (HH:MM:SS) field to the final version of my database).
Let SQL return the dates.. it can sort on the dates, and search on the dates.
SELECT * FROM Links Where Add_Date < current_date()
You can also change the date format to almost anything (look in the middle of the mysql book for a good table).
The problem with Timestamp is that it's an auto-update field. Every time the database record is accessed it changes. It's sort of a 'date of last mod' field. That would not be a bad idea for the 'updated' field, except (or because) Admin modifications would be recorded as well as user mods.
I have added a "Time" field to the record, and that is probably the easiest way to do it. That way you can easily sort by time_of_day to see when most activity is, etc.
The time I use is HH:MM:SS and it works just fine through the DBSQL.pm interface with the Links table.
I probably would change the Mod_Date to a timestamp and add a TimeOfDay (HH:MM:SS) field to the final version of my database).