Re: [BUGS] BUG #1179: Time comparison fail

2004-06-27 Thread Mauricio CASTRO
You are right! I am doing something wrong? I understand that there is a difference but I don't know why. mex2=# select mex2-# age(endeddatetime,starteddatetime), mex2-# time, mex2-# date_part('second',(age(endeddatetime,starteddatetime)))*1000, mex2-# date_part('second',(age(endeddatetime

Re: [BUGS] BUG #1179: Time comparison fail

2004-06-22 Thread Stephan Szabo
On Tue, 22 Jun 2004, Mauricio CASTRO wrote: > You are right! > > I am doing something wrong? I understand that there is a difference but I > don't know why. Floating point math is inexact. The date_part(...) is returning a value that is very close to, but not exactly 4.031 due to accuracy limita

Re: [BUGS] BUG #1179: Time comparison fail

2004-06-22 Thread Stephan Szabo
On Tue, 22 Jun 2004, PostgreSQL Bugs List wrote: > must_betrue is false for the query bellow One of those is a bigint, the other is a double expression that is probably very slightly different from the integer you're comparing it to. What is the result of the date_part(...)-time? --

[BUGS] BUG #1179: Time comparison fail

2004-06-22 Thread PostgreSQL Bugs List
The following bug has been logged online: Bug reference: 1179 Logged by: Mauricio CASTRO ESPINOSA Email address: [EMAIL PROTECTED] PostgreSQL version: 7.2.4 Operating system: RedHat 7.3 uname:Linux Play 2.4.18-3 #1 Thu Apr 18 07:37:53 EDT 2002 i686 unknown Description: