From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "yoursoft" <yoursoft(at)freemail(dot)hu>, <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: Missing PgAdmin Feature |
Date: | 2006-08-03 10:15:01 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E40154C3FD@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
> -----Original Message-----
> From: pgadmin-support-owner(at)postgresql(dot)org
> [mailto:pgadmin-support-owner(at)postgresql(dot)org] On Behalf Of yoursoft
> Sent: 03 August 2006 11:13
> To: pgadmin-support(at)postgresql(dot)org
> Subject: [pgadmin-support] Missing PgAdmin Feature
>
> Dear Developers,
>
> Create varchar index with command:
> CREATE INDEX name ON table (colum text_pattern_ops);
>
> When you select index or table in left tree, In the reversed
> sql window
> you will see:
> CREATE INDEX name
> ON table
> USING btree
> (column);
>
> In the properties window of index you see:
> operator classes: text_pattern_ops
>
> I think in the reversed sql window should be:
> CREATE INDEX name ON table (colum text_pattern_ops);
>
> If you backup the table, you will find in the sql script:
> CREATE INDEX name ON table (colum text_pattern_ops);
> (it is good)
Already fixed for 1.6.0:
2006-06-13 DP 1.6.0 Display non-default op classes in index
definitions.
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | George Pavlov | 2006-08-03 10:50:48 | Re: pgAdmin 1.4.3 bug with delete button in win32 |
Previous Message | yoursoft | 2006-08-03 10:12:34 | Missing PgAdmin Feature |