Presumably, but that is not what I was doing. I was taking a number from a user, which was supposed to be divisible by an integer. Sometimes the user left off the last digit when typing in the number or otherwise typed it in wrong, rendering the input not divisible by that number.
So it was looking for something like 4.345. Gabriel _________________ Gabriel Weinberg [EMAIL PROTECTED] -----Original Message----- From: Stephan Szabo [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 11:35 AM To: Gabriel Weinberg Cc: 'Bruno Wolff III'; [EMAIL PROTECTED] Subject: Re: [BUGS] Sequential Scan Index Bug On Wed, 7 Apr 2004, Gabriel Weinberg wrote: > Yes, I thought I had done that, but now that I figured out what was > going on, I did it for all cases. So it is no longer occurring for > me, but it still seems like a bug in PostgreSQL. I would expect it to > throw an error immediately, instead of scanning the table for a value > of a different type. But what if you said id = 4.0? Would you want it to find the id=4 row? ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
