database - DB Design: Sort Order for Lookup Tables -


I have an application where the database 15 for tables in the back-end of a table, for example, such County is:

  CountyID (P) county 49001 Beaver 49005 cache 49007 carbon 49009 Daggett 49011 Davis 49015 Emery 49029 Morgan 49031 Piute 49,033 Rich 49035 Salt Lake 49037 San Juan 49041 Sevier 49043 Summit 49045 Tooele 49049 Utah 49051 Wasatch 49057 Weber  

UI for the application of the various places to see these tables A number of Mbo boxes, and lists in this case have asked my client boxes:

  CountyID (P) to rest County 49035 Salt Lake 49049 Utah 49011 Davis 49057 Weber 49045 Tooele ' spectrum  

the best plan I told me I have a partner to add a column to each lookup table for the sort order (numerical) is to accomplish this, he thought that table 3 General To violate the form Was caused, but I think it depends on the sort order is still alphabet rest of the key and only key (even if the list).

Is the SortOrder column the best way to do this, or am I not seeing it now?

I have a good way to go in order columns in a way that agrees with @cletus and 3NF does not infringe (because, as you said, sort order column entries are dependent on the candidate key of the functional table).

I am not sure that I believe that alphanumeric numeric is better than that. In the specific case of counties, rarely new ones are built. But there is no requirement that the specified number is sequential; You can allocate with numbers that are a multi-million one hundred, for example, leaving enough room for the inclusion.


Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -