(1.8RC1)
If for some unusual reason I want to use pgadmin to add a column named:
one "two" three
Then I am able to specify this identifier as
"one ""two"" three"
but pgadmin will always show it as
one "two" three
Which I think is ok, but it shows it in generated SQL as
"one "two" three"
i
Hi,
I'm not sure if this is a general problem but here's the steps I
undertook:
Running IBM T43 w/WinXP SP2 / current patches (+special patch for >1GB
hibernation)
Running PgAdmin 1.8 beta 5 connected to local pg server with sql window
open
Put computer into Hibernation
Woke it up
SQL win
[EMAIL PROTECTED] wrote:
"~/Library/Preferences/pgadmin3 preferences" on your system? Any change
if you remove it?
>>> I have no such file in ~/Library/Preferences or in /Library/Preferences
>> OK. Can you tell me what the output from the following commands is
>> ple
Dave Page a écrit :
> Guillaume Lelarge wrote:
>> Dave Page a écrit :
>>> Guillaume Lelarge wrote:
> I guess the general ordering of the statements should be as follows:
> 1 Any ALTER SEQUENCE MIN/MAXVALUE statements that widen the range
> 2 SETVAL
> 3 Any ALTER SEQUENCE MIN/MAXVALU
[EMAIL PROTECTED] wrote:
>> "~/Library/Preferences/pgadmin3 preferences" on your system? Any change
>> if you remove it?
> I have no such file in ~/Library/Preferences or in /Library/Preferences
OK. Can you tell me what the output from the following commands is please:
ot
Guillaume Lelarge wrote:
> Dave Page a écrit :
>> Guillaume Lelarge wrote:
I guess the general ordering of the statements should be as follows:
1 Any ALTER SEQUENCE MIN/MAXVALUE statements that widen the range
2 SETVAL
3 Any ALTER SEQUENCE MIN/MAXVALUE statements that narrow the
Horvath Gabor wrote:
> On 9/24/07, Dave Page <[EMAIL PROTECTED]> wrote:
>> Horvath Gabor wrote:
>>> pgAdminIII v1.8-Beta5
>>> Windows XP
>>> PostgreSQL 8.1, linux
>>>
>>> I tried to adjust the Minimum value in the properties dialog of a sequence.
>>> I wanted to adjust the range so that the present
Dave Page a écrit :
> Guillaume Lelarge wrote:
>>> I guess the general ordering of the statements should be as follows:
>>> 1 Any ALTER SEQUENCE MIN/MAXVALUE statements that widen the range
>>> 2 SETVAL
>>> 3 Any ALTER SEQUENCE MIN/MAXVALUE statements that narrow the range.
>>>
>> We can't add this
Guillaume Lelarge wrote:
>> I guess the general ordering of the statements should be as follows:
>> 1 Any ALTER SEQUENCE MIN/MAXVALUE statements that widen the range
>> 2 SETVAL
>> 3 Any ALTER SEQUENCE MIN/MAXVALUE statements that narrow the range.
>>
>
> We can't add this kind of functionnality n
Horvath Gabor a écrit :
> On 9/24/07, Dave Page <[EMAIL PROTECTED]> wrote:
>> Horvath Gabor wrote:
>>> pgAdminIII v1.8-Beta5
>>> Windows XP
>>> PostgreSQL 8.1, linux
>>>
>>> I tried to adjust the Minimum value in the properties dialog of a sequence.
>>> I wanted to adjust the range so that the pres
On 9/24/07, Dave Page <[EMAIL PROTECTED]> wrote:
> Horvath Gabor wrote:
> > pgAdminIII v1.8-Beta5
> > Windows XP
> > PostgreSQL 8.1, linux
> >
> > I tried to adjust the Minimum value in the properties dialog of a sequence.
> > I wanted to adjust the range so that the present current value would
> >
11 matches
Mail list logo
