Re: bigint and unix time

Поиск
Список
Период
Сортировка
От Janiv Ratson
Тема Re: bigint and unix time
Дата
Msg-id 25B9D8D6D61CDB4CAD5D742B947F5C1A0493824C@ES-EX2010A-IL.essencesecurity.com
обсуждение исходный текст
Ответ на Re: bigint and unix time  (Adrian Klaver <adrian.klaver@gmail.com>)
Список pgsql-sql
Hi and thanks,
If my 'time' column is being saved as bigint: 1287323899000000.
How do I write a query to check if the 'time' field is greater than now - 30 (past 30 days)?

Thanks,
Janiv,.

-----Original Message-----
From: Adrian Klaver [mailto:adrian.klaver@gmail.com]
Sent: Sunday, August 14, 2011 20:57
To: pgsql-sql@postgresql.org
Cc: Janiv Ratson
Subject: Re: [SQL] bigint and unix time

On Sunday, August 14, 2011 4:13:30 am Janiv Ratson wrote:
> Hi,
>
>
>
> I have the following query:
>
>
>
> select ticket as ticket, time as created, author as reporter,
> cast(extract(epoch from (date 'now' - integer '30')) as bigint)
>
> from ticket_change tc
>
> where field = 'status'
>
> and newvalue = 'reopened'
>
> and time > extract(epoch from (date 'now' - integer '30'))
>
> order by time
>
>
>
> I'm trying it get all records that their 'time' is within the past 30
> days.
>
> However, the time is bigint: 1287323899000000
>
> While the extract(epoch from (date 'now' - integer '30')) is 1310677200

Bigint versus integer refers to the max values that the field can contain.  For a
given value of integer the storage should be the same for each up to the limit
of the integer field. Would seem that whatever is putting values into time is
inflating the values if they are actually referring to contemporary time values.

>
>
>
> As you understand, I always get all records ...
>
>
>
> How do I solve it?
>
>
>
> Thanks,
>
> Janiv.
>


--
Adrian Klaver
adrian.klaver@gmail.com




В списке pgsql-sql по дате отправления:

Предыдущее
От: Adrian Klaver
Дата:
Сообщение: Re: bigint and unix time
Следующее
От: David Harel
Дата:
Сообщение: Re: pgadmin debugger