On 2012-01-27, bbo...@free.fr bbo...@free.fr wrote:
Hello!
again quite a stupid problem i regularly run into
and that i still haven't solved yet...
again i used a type timestamp to keep a track of modification time,
and again it gets stupid and confusing.
oops! (when
On Fri, Jan 27, 2012 at 08:17:37AM -0800, Adrian Klaver wrote:
Did some digging. php-mktime returns the Unix epoch (seconds since January 1
1970 00:00:00 GMT)
indeed, didn't get it that postgres timestamp wasn't the same
Postgres has a function(to_timestamp) that will convert that to a
On Saturday, January 28, 2012 1:43:43 am Bruno Boettcher wrote:
On Fri, Jan 27, 2012 at 08:17:37AM -0800, Adrian Klaver wrote:
Did some digging. php-mktime returns the Unix epoch (seconds since
January 1 1970 00:00:00 GMT)
indeed, didn't get it that postgres timestamp wasn't the same
Hello!
again quite a stupid problem i regularly run into
and that i still haven't solved yet...
again i used a type timestamp to keep a track of modification time, and again
it gets stupid and confusing.
first of all the errors are labeled as timestamp without timezone, i only
On Friday, January 27, 2012 7:44:55 am bbo...@free.fr wrote:
Hello!
again quite a stupid problem i regularly run into
and that i still haven't solved yet...
again i used a type timestamp to keep a track of modification time, and
again it gets stupid and confusing.
first of all
On 1/27/2012 9:44 AM, bbo...@free.fr wrote:
Hello!
again quite a stupid problem i regularly run into
and that i still haven't solved yet...
again i used a type timestamp to keep a track of modification time, and again
it gets stupid and confusing.
first of all the errors are labeled
On Friday, January 27, 2012 7:44:55 am bbo...@free.fr wrote:
Hello!
again quite a stupid problem i regularly run into
and that i still haven't solved yet...
again i used a type timestamp to keep a track of modification time, and
again it gets stupid and confusing.
first of all
