Hi all,

Congrats on 1.6 - I love it! This may have been fixed in beta 2
(which I don't have yet), but just in case -

I've noticed an inconsistency in the naming of data types between
creating the columns in a table and altering them afterwards. The
dialog for creating columns uses the standard names such as
"character varying", etc, but the dialog for altering columns uses
the abbreviated forms, such as "varchar".

Thanks for all the hard work and a great tool.

--Ray O'Donnell.


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

Raymond O'Donnell
Director of Music, Galway Cathedral, Galway, Ireland
rod@iol.ie
----------------------------------------------------------------------



---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

> -----Original Message-----
> From: pgadmin-support-owner@postgresql.org
> [mailtogadmin-support-owner@postgresql.org] On Behalf Of
> Raymond O'Donnell
> Sent: 06 October 2006 15:41
> To: pgadmin-support@postgresql.org
> Subject: [pgadmin-support] Inconsistency in data types
>
> Hi all,
>
> Congrats on 1.6 - I love it! This may have been fixed in beta 2
> (which I don't have yet), but just in case -
>
> I've noticed an inconsistency in the naming of data types between
> creating the columns in a table and altering them afterwards. The
> dialog for creating columns uses the standard names such as
> "character varying", etc, but the dialog for altering columns uses
> the abbreviated forms, such as "varchar".
>
> Thanks for all the hard work and a great tool.

Hi Ray,

Thanks for the feedback - I've fixed this for beta 3.

Regards, Dave.

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

I had similar problem with 1.6 b 1, It was possible to create tables
only with "character varying", not varchar.
And problem was when trying to insert/delete from such table I got
message about "character varying" type cannot be found. I can't
reproduce this with b2 so it may be fixed?

Regards.

On 10/6/06, Dave Page <dpage@vale-housing.co.uk> wrote:
>
>
> > -----Original Message-----
> > From: pgadmin-support-owner@postgresql.org
> > [mailtogadmin-support-owner@postgresql.org] On Behalf Of
> > Raymond O'Donnell
> > Sent: 06 October 2006 15:41
> > To: pgadmin-support@postgresql.org
> > Subject: [pgadmin-support] Inconsistency in data types
> >
> > Hi all,
> >
> > Congrats on 1.6 - I love it! This may have been fixed in beta 2
> > (which I don't have yet), but just in case -
> >
> > I've noticed an inconsistency in the naming of data types between
> > creating the columns in a table and altering them afterwards. The
> > dialog for creating columns uses the standard names such as
> > "character varying", etc, but the dialog for altering columns uses
> > the abbreviated forms, such as "varchar".
> >
> > Thanks for all the hard work and a great tool.
>
> Hi Ray,
>
> Thanks for the feedback - I've fixed this for beta 3.
>
> Regards, Dave.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings