Bug #559: MACADDR type & 00:00:00:00:00:00

From: pgsql-bugs(at)postgresql(dot)org
To: pgsql-bugs(at)postgresql(dot)org
Subject: Bug #559: MACADDR type & 00:00:00:00:00:00
Date: 2002-01-11 10:18:34
Message-ID: 200201111018.g0BAIYt88595@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Michael Handler (handler(at)grendel(dot)net) reports a bug with a severity of 3
The lower the number the more severe it is.

Short Description
MACADDR type & 00:00:00:00:00:00

Long Description
postgresql version 7.1.3, compiled with gcc 2.95.2 on solaris 2.6, running on solaris 2.8.

provisioning=> \d enduser
Table "enduser"
Attribute | Type | Modifier
-----------------+-------------------+----------------------------
account | character varying | not null
active | boolean | not null default 't'::bool
isp_id | integer | not null
speed_plan_id | integer | not null
service_plan_id | integer | not null
node_id | integer | not null
cm_macaddr | macaddr | not null
Indices: enduser_cm_macaddr_key,
enduser_pkey

provisioning=> insert into enduser values ('2', 't', 1, 1, 1, 1, '00:00:00:00:00:00');
INSERT 20853 1
provisioning=> select account,cm_macaddr from enduser where account = '2';
account | cm_macaddr
---------+------------
2 |
(1 row)

provisioning=> select count(*) from enduser where cm_macaddr is null;
count
-------
0
(1 row)

it's not null, so shouldn't it be retrieving as '00:00:00:00:00:00'?
not that i ever expect to encounter that macaddress in the field, but
for consistency's sake...

i just tested 'ff:ff:ff:ff:ff:ff', and it works fine.

ps postgresql sends mysql running back home to mommy. you guys are my heroes.

Sample Code

No file was uploaded with this report

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message pgsql-bugs 2002-01-11 13:45:51 Bug #560: ODBC problem at migrating 7.0 to 7.1
Previous Message Dmitry Macsema 2002-01-11 00:54:40 Bad integer