This is a discussion on BUG #4277: Feature request inet type cast numeric values within the pgsql Bugs forums, part of the PostgreSQL category; --> The following bug has been logged online: Bug reference: 4277 Logged by: x Email address: noreply@postgresql.org PostgreSQL version: n/a ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| The following bug has been logged online: Bug reference: 4277 Logged by: x Email address: noreply@postgresql.org PostgreSQL version: n/a Operating system: n/a Description: Feature request inet type cast numeric values Details: SELECT inet 2130706433; Should return: ?column? -------- 127.0.0.1 This would emulate the functionality: CREATE OR REPLACE FUNCTION inet_ntoa(bigint) RETURNS text AS ' SELECT (($1>>24) & 255::int8) || ''.'' || (($1>>16) & 255::int8) || ''.'' || (($1>>8) & 255::int8) || ''.'' || ($1 & 255::int8) as result ' LANGUAGE 'SQL'; -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs |
| |||
| x wrote: > Description: Feature request inet type cast numeric values > Details: > > SELECT inet 2130706433; > > Should return: > ?column? > -------- > 127.0.0.1 > > This would emulate the functionality: > CREATE OR REPLACE FUNCTION inet_ntoa(bigint) RETURNS text AS ' > SELECT (($1>>24) & 255::int8) || ''.'' || > (($1>>16) & 255::int8) || ''.'' || > (($1>>8) & 255::int8) || ''.'' || > ($1 & 255::int8) as result > ' > LANGUAGE 'SQL'; You can create the cast yourself if you want to, see CREATE CAST. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs |
| ||||
| "Heikki Linnakangas" <heikki@enterprisedb.com> writes: >> Description: Feature request inet type cast numeric values > You can create the cast yourself if you want to, see CREATE CAST. The proposed cast seems rather inappropriate in an IPv6 world anyway. If you want IPv4-only functionality, I think the inet4 type on pgfoundry has this behavior already. regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs |