Re: Sorting Challenge
От | |
---|---|
Тема | Re: Sorting Challenge |
Дата | |
Msg-id | 20050831055134.64564.qmail@web33312.mail.mud.yahoo.com обсуждение исходный текст |
Ответ на | Re: Sorting Challenge (Bruno Wolff III <bruno@wolff.to>) |
Ответы |
PGSQL, Fedora core 3 and a PII 400 MHz Box
Re: Sorting Challenge |
Список | pgsql-novice |
> On Tue, Aug 30, 2005 at 15:58:40 -0700, > operationsengineer1@yahoo.com wrote: > > > > i have a lot more data like this, but i want to > keep > > it simple. the first two alphas represent an area > and > > the foloowing digit(s) represent a unique id. > > > > the data is currently held in a text field. > > It generally isn't a good idea to store multiple > fields in one column. > You should probably split this into two columns > unless there is a significant > performance problem with doing so. > > If there is than you might try creating an operator > class that properly > compares these strings. Then you can use that > operator class to do sorts > or create btree indexes. hi Bruno, the code is actually a single field. the reason it isn't just a numeric value is b/c i thought there would be value in making the code somewhat human readable. as it stands now, a person can look at the defect code and know will know the causal process. is there a better way to make the code semi-human readable and still act as a defect code (and primary key)? tia... __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
В списке pgsql-novice по дате отправления: