Re: Function trunc() behaves in unexpected manner with different data types
От | Alvaro Herrera |
---|---|
Тема | Re: Function trunc() behaves in unexpected manner with different data types |
Дата | |
Msg-id | 1298648330-sup-361@alvh.no-ip.org обсуждение исходный текст |
Ответ на | Re: Function trunc() behaves in unexpected manner with different data types (Merlin Moncure <mmoncure@gmail.com>) |
Ответы |
Re: Function trunc() behaves in unexpected manner with
different data types
|
Список | pgsql-bugs |
Excerpts from Merlin Moncure's message of vie feb 25 12:28:25 -0300 2011: > no I wouldn't, and the pg_dump extra_float_digits setting addresses my > primary concern. The client has a similar issue though -- suppose it > fetches a value from the server and updates it back -- which record > gets the update? You would get different results if the client was > using binary or text features of the protocol. Not saying this is > wrong or needs to be fixed, just pointing it out :-). > > update foo set val=val + 1 where val = 2183.68; I think the mere idea of using floating point equality on a WHERE clause is bogus, regardless of text or binary format. -- Ãlvaro Herrera <alvherre@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support
В списке pgsql-bugs по дате отправления: