Skip site navigation (1) Skip section navigation (2)

bug: Bit String Types / question: edit view

From: "Pfuetz, Michael" <Michael(dot)Pfuetz(at)SARTORIUS(dot)com>
To: <pgadmin-support(at)postgresql(dot)org>
Subject: bug: Bit String Types / question: edit view
Date: 2007-01-10 08:15:25
Message-ID: CEA9200E8DACA943855F9AB11C3D7A472C5D00@GONEXCL2.Sartorius.com (view raw or flat)
Thread:
Lists: pgadmin-support
Hello,

i think there are 2 bugs in pgadmin:
CREATE TABLE test_bit
(
  id text NOT NULL,
  byte bit(8) NOT NULL,
  CONSTRAINT test_bit_pkey PRIMARY KEY (id)
) 
WITHOUT OIDS;
ALTER TABLE test_bit OWNER TO assux;

Insert with pgadmin:
hello,10101010
German error: Länge der Bitkette 1 stimmt nicht mit Typ bit(8) überein
my translation: The length of the Bit string 1 is not conform to type bit(8)

Insert with psql:
INSERT INTO test_bit (id,byte) VALUES ('hello', B'10101010');
INSERT 0 1

-------------------

CREATE OR REPLACE FUNCTION test_procedure(IN bit1 "bit", OUT bit_out "bit") AS
$BODY$DECLARE
BEGIN
  bit_out := bit1;
END;$BODY$
  LANGUAGE 'plpgsql' VOLATILE;
ALTER FUNCTION test_procedure(IN bit1 "bit", OUT bit_out "bit") OWNER TO assux;

by editing with pgadmin the resolve sql-statment is wrong (""bit""):
CREATE OR REPLACE FUNCTION test_procedure(IN bit1 ""bit"", OUT bit_out ""bit"") AS
$BODY$DECLARE
BEGIN
  bit_out := bit1;
END;$BODY$
LANGUAGE 'plpgsql' VOLATILE;

-------------------

Is it possible to edit an view with pgadmin? I add the rules:
ON UPDATE TO,
ON INSERT TO,
ON DELETE TO

My Pgadmin Version:
1.6.2 (Jan 6 2007, rev: 5837), Windows XP, SP2
1.6.2 (Dec 14 2006, rev: 5784), SuSE Linux 10.0

I hope you can help my.

Best regards

Michael Pfütz




Disclaimer : 

The information contained in this e-mail is intended only for the individual
addressed. If you have received this e-mail by mistake, please notify us
immediately by return reply. Be sure to delete this message and all its
attachments from your system. Please note that any unauthorized review,
copying, disclosure or any other use of this information is strictly
prohibited. E-mail transmission cannot be guaranteed to be secure or
error-free as information could be intercepted, corrupted, lost, destroyed,
received late or incomplete, or could contain viruses. The sender therefore
does not accept any liability for any error or omission in the content of
this message, either of which are caused as a result of e-mail transmission.
If verification is required, please request a hard-copy version. 
Thank you.

pgadmin-support by date

Next:From: Dave PageDate: 2007-01-10 08:46:16
Subject: Re: Re : Backup file not UTF-8 (introduced bug
Previous:From: Mathias DurstDate: 2007-01-10 08:08:31
Subject: Bug in Exporter V1.6.X

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group