| From: | "Joris Dobbelsteen" <Joris(at)familiedobbelsteen(dot)nl> |
|---|---|
| To: | "Melvin Davidson" <mdavidson(at)cctus(dot)com> |
| Cc: | <pgadmin-support(at)postgresql(dot)org> |
| Subject: | Re: Server order |
| Date: | 2007-05-22 23:11:48 |
| Message-ID: | 73427AD314CC364C8DF0FFF9C4D693FF037B3E@nehemiah.joris2k.local |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
________________________________
From: pgadmin-support-owner(at)postgresql(dot)org
[mailto:pgadmin-support-owner(at)postgresql(dot)org] On Behalf Of Melvin
Davidson
Sent: dinsdag 22 mei 2007 22:30
To: Mike(dot)Blackwell(at)rrd(dot)com; pgadmin-support(at)postgresql(dot)org
Subject: Re: [pgadmin-support] Server order
Unfortunately, it is currently not that easy because that
information is stored in the Windows registry.
No for comment, but I cannot imagine how the display order is so
directly related to the registry. Generally sorting before displaying
doesn't seem to be such a complicated feature.
Most likely you are meaning that you are using the position in the list
to reference information in the registry. Can't this be solved by a
simple lookup table translating display-order to storage-order?
- Joris Dobbelsteen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Leszek Trenkner | 2007-05-23 01:21:24 | Re: Server order |
| Previous Message | Melvin Davidson | 2007-05-22 21:45:58 | Re: Server order |