Re: [PATCH] Add get_bytes() and set_bytes() functions
От | Aleksander Alekseev |
---|---|
Тема | Re: [PATCH] Add get_bytes() and set_bytes() functions |
Дата | |
Msg-id | CAJ7c6TM=-VbMQ7vVBD3BrwmT-1Yt2pF6q0kZcC01rzxd74zjkA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [PATCH] Add get_bytes() and set_bytes() functions (Dean Rasheed <dean.a.rasheed@gmail.com>) |
Ответы |
Re: [PATCH] Add get_bytes() and set_bytes() functions
|
Список | pgsql-hackers |
Hi, > Perhaps we should also add casts between bytea and the integer/numeric > types. That might be easier to use than functions in some > circumstances. > > When casting a numeric to an integer, the result is rounded to the > nearest integer, and NaN/Inf generate errors, so we should probably do > the same here. Yes, I was also thinking about adding NUMERIC versions of get_bytes() / set_bytes(). This would allow converting more than 8 bytes to/from an integer. I dropped this idea because I thought there would be not much practical use for it. On the flip side you never know who uses Postgres and for what purpose. I will add corresponding casts unless the idea will get a push-back from the community. IMO the existence of these casts will at least not make things worse. -- Best regards, Aleksander Alekseev
В списке pgsql-hackers по дате отправления: