From: | Ivan <Ivan-Sun1(at)mail(dot)ru> |
---|---|
To: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
Cc: | pgadmin-support(at)postgresql(dot)org |
Subject: | Re: Composite type creation issues |
Date: | 2005-11-03 08:08:27 |
Message-ID: | 379887043.20051103110827@mail.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Hello Dave,
Tuesday, November 1, 2005, 12:01:55 AM, you wrote:
DP>
>> -----Original Message-----
>> From: pgadmin-support-owner(at)postgresql(dot)org
>> [mailto:pgadmin-support-owner(at)postgresql(dot)org] On Behalf Of Ivan
>> Sent: 29 October 2005 10:05
>> To: pgadmin-support(at)postgresql(dot)org
>> Subject: [pgadmin-support] Composite type creation issues
>>
>> Hello,
>>
>> PgAdmin 1.4.0beta3.
>>
>> There are two issues with composite type creation:
>> - when you add numeric field, precision text box is disabled and
>> lenght textbox value is discarded
>> - field names aren't quoted automaticaly
>>
>> Thank you for support.
DP> Thanks Ivan, fixes committed to SVN.
I download last snapshot of PgAdmin (2 Nov) and see that
Length and Precision attributes of numeric fields of a composite type
are discarded, i.e. in resulting SQL numeric fields are always:
...
"NumericField" numeric
...
no matter what lenght and precision you specify.
Thank you for support.
--
Best regards,
Ivan mailto:Ivan-Sun1(at)mail(dot)ru
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2005-11-03 09:18:36 | Re: Composite type creation issues |
Previous Message | Andreas Pflug | 2005-11-02 13:32:04 | Re: pgAdminIII does not respect proxy-settings |