Re: Timestamp Length or Precision Bug

["Dave Page" <dpage(at)pgadmin(dot)org>]

On Feb 8, 2008 12:40 AM, Adam Taft <adam(at)adamtaft(dot)com> wrote:
> Hi,
>
> I've noticed this bug for quite a few versions of PgAdmin now.  I was
> hoping that a bug reporting tool would someday appear on the website.  I
> guess this is the best way to report the problem.

That is the correct method.

> When creating a 'timestamp without timezone' and specifying the 'length'
> parameter, invalid SQL is generated.  The generated SQL is this:
>
> ALTER TABLE usertags ADD COLUMN a timestamp without time zone(3);

Thanks, fixed in SVN for 1.8.3.

> Additionally, the 'length' field is used in the PgAdmin UI, whereas in
> the PostgreSQL documention, the field is referred to as 'precision.'
> I'm wondering if the Precision input box in the PgAdmin UI should be
> enabled instead of the Length input box.

I'm not so worried about that - everyone know what it means and it's
more than just a couple of lines of code to change it.

-- 
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Oracle-compatible database company