|
Home > Archive > Pgadmin > October 2006 > pgAdmin3 1.6b2: edit grid: glitch with boolean value NULL
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
pgAdmin3 1.6b2: edit grid: glitch with boolean value NULL
|
|
| Erwin Brandstetter 2006-10-25, 8:27 am |
| Hi developers!
I am testing pgAdmin III Beta 2 (Oct 3 2006, re: 5426:5427) on Windows
XP (latest patch level).
RDBMS is PG 8.1.4 on a remote debian sarge server. (PG from backports.org).
Connected via SSH-tunnel with port forwarding.
pgAdmin not being able to display NULL values in boolean fields has been
a major bug in v1.4.3. Fortunately, this has been remedied in v1.6 - if
not completely.
When I activate a boolean field an keep pressing the space bar, the
value cycles between TRUE, FALSE and NULL. Also works, when I keep
clicking _on_ the small checkbox in the field. So far so good. But if I
click in the field, outside the little box, the the value only toggles
between TRUE and FALSE. I don't assume this is on purpose?
Regards
Erwin Brandstetter
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
| |
| Dave Page 2006-10-25, 8:27 am |
|
> -----Original Message-----
> From: pgadmin-support-owner@postgresql.org
> [mailto:pgadmin-support-owner@postgresql.org] On Behalf Of
> Erwin Brandstetter
> Sent: 07 October 2006 17:47
> To: pgadmin-support@postgresql.org
> Subject: [pgadmin-support] pgAdmin3 1.6b2: edit grid: glitch
> with boolean value NULL
>
> When I activate a boolean field an keep pressing the space bar, the
> value cycles between TRUE, FALSE and NULL. Also works, when I keep
> clicking _on_ the small checkbox in the field. So far so
> good. But if I
> click in the field, outside the little box, the the value
> only toggles
> between TRUE and FALSE. I don't assume this is on purpose?
Actually it was, but in hindsight I'm not sure it was the best design.
I've committed a change to SVN that corrects this.
Thanks, Dave.
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
|
|
|
|
|