Now there should be no more incorrect dates as - or rather if they are incorrect it's the fault of the server's date/time rather than whoever is submitting news.
When trying to fix this little glitch I found out something interesting about MySQL. It appears the MySQL (what this hosting company runs) doesn't allow for the results of functions (such as NOW()) to be the default value for columns - which makes it somewhat hard to have a column just track when something was posted. Sure there is the TIMESTAMP type that has this functionality sort of built in but that just screams "crappy work around".
So it appears the answer to the Linux/OpenSource question "why would anyone pay for software when free software is available" would be something along the lines of "when you want something without gaping holes in its feature set.
When trying to fix this little glitch I found out something interesting about MySQL. It appears the MySQL (what this hosting company runs) doesn't allow for the results of functions (such as NOW()) to be the default value for columns - which makes it somewhat hard to have a column just track when something was posted. Sure there is the TIMESTAMP type that has this functionality sort of built in but that just screams "crappy work around".
So it appears the answer to the Linux/OpenSource question "why would anyone pay for software when free software is available" would be something along the lines of "when you want something without gaping holes in its feature set.
