Re: Show NULL values AS <NULL> not working

------=_Part_9559_6274211.1200350997987
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi guys,

A bit more info.

If I write a query manually (i.e. SELECT * FROM table) then the column
shows
up as "<NULL>" which is what I expect.
However, if I write click the table and hit the "View Data" menu option,
the
column is blank.

Andy.

On 1/14/08, Andy Shellam <andy.shellam-lists@[EMAIL PROTECTED]
> wrote:
>
> Hi Dave and team,
>
> Another slight bug (I think):
>
> I have a table which has a column called "first_invalid" which should be
a
> timestamp if the record is invalid, or NULL if it's valid.
> In PgAdmin I have the "Show NULL values as <NULL>" option enabled, but
it
> still displays a blank cell for this column.
>
> The reason why I think it may not be a bug, is I tried doing this:
>
> "SELECT COALESCE(first_invalid, '<NULL>') AS first_invalid FROM table"
>
> but PostgreSQL threw it out because "<NULL>" is not a valid timestamp -
> instead I had to do:
>
> "SELECT COALESCE(first_invalid, '1900-01-01') AS first_invalid FROM
table"
>
> to prove the column is in fact NULL, and I do get: "1900-01-01
> 00:00:00+00" for this record, but in the data entry grid, PgAdmin still
> displays it blank.
>
> Question: is this a bug, or intended behaviour?
>
> Thanks,
>
> Andy
>

------=_Part_9559_6274211.1200350997987
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi guys,<br><br>A bit more info.<br><br>If I write a query manually (i.e.
SELECT * FROM table) then the column shows up as &quot;&lt;NULL&gt;&quot;
which is what I expect.<br>However, if I write click the table and hit the
&quot;View Data&quot; menu option, the column is blank.
<br><br>Andy.<br><br><div><span class="gmail_quote">On 1/14/08, <b
class="gmail_sendername">Andy Shellam</b> &lt;<a
href="mailto:andy.shellam-lists@[EMAIL PROTECTED]
">andy.shellam-lists@[EMAIL PROTECTED]
>&gt;
wrote:</span>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204,
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Dave and
team,<br><br>Another slight bug (I think):<br><br>I have a table which has
a column called &quot;first_invalid&quot; which should be a timestamp if
the record is invalid, or NULL if it&#39;s valid.
<br>In PgAdmin I have the &quot;Show NULL values as &lt;NULL&gt;&quot;
option enabled, but it still displays a blank cell for this column.
<br><br>The reason why I think it may not be a bug, is I tried doing
this:<br><br>&quot;SELECT COALESCE(first_invalid, &#39;&lt;NULL&gt;&#39;)
AS first_invalid FROM table&quot;<br><br>but PostgreSQL threw it out
because &quot;&lt;NULL&gt;&quot; is not a valid timestamp - instead I had
to do:
<br><br>&quot;SELECT COALESCE(first_invalid, &#39;1900-01-01&#39;) AS
first_invalid FROM table&quot;<br><br>to prove the column is in fact NULL,
and I do get: &quot;1900-01-01 00:00:00+00&quot; for this record, but in
the data entry grid, PgAdmin still displays it blank.
<br><br>Question: is this a bug, or intended
behaviour?<br><br>Thanks,<br><span class="sg"><br>Andy<br>
</span></blockquote></div><br>

------=_Part_9559_6274211.1200350997987--