From: | "Joe Kramer" <cckramer(at)gmail(dot)com> |
---|---|
To: | pgadmin-support(at)postgresql(dot)org |
Subject: | Re: Inconsistency in data types |
Date: | 2006-10-06 15:44:48 |
Message-ID: | b4c00a110610060844v3b66bcaaic0160810ccf35a92@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
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(at)vale-housing(dot)co(dot)uk> wrote:
>
>
> > -----Original Message-----
> > From: pgadmin-support-owner(at)postgresql(dot)org
> > [mailto:pgadmin-support-owner(at)postgresql(dot)org] On Behalf Of
> > Raymond O'Donnell
> > Sent: 06 October 2006 15:41
> > To: pgadmin-support(at)postgresql(dot)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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Lelarge | 2006-10-06 15:59:18 | Re: Inconsistency in data types |
Previous Message | Dave Page | 2006-10-06 15:28:25 | Re: Inconsistency in data types |