dhtmlxGrid如何选择值进行排序？(dhtmlxGrid How to select the value for sorting?)

 “做任何事的最快方式都不是要这样做。” - Cary Millsap， 优化Oracle性能 。 
 
 “一位设计师知道他已经实现了真正的优雅，而不是什么都没有剩下，但是什么时候什么都没有了。” - Antoine de Saint-Exupéry 
 
 更简单的实现有两个表和三个索引，两个独特。 更复杂的实现有三个表和五个索引，四个独特。 asso_countries_players.player_name上的索引（ 应该是代理 asso_countries_players.player_name 如果玩家的名字发生变化，比如他们结婚或者合法地改变它，如Chad Ochocinco（nee Johnson）所做的那样，会发生什么？）也必须是唯一的，以执行0..1球员和国家之间关系的性质。 
 
 如果数据模型不需要关联实体，则将其消除。 将0..1关系或1..n关系转换为n..n关系通常很简单： 
 
 
 
 添加关联实体（除非关系本身具有属性，比如开始或结束日期，否则我会质疑需要替代关键字） 
 
 
 用现有数据填充关联实体 
 
 
 重新实现外键约束 
 
 
 删除子表中被取代的外键列。 
 

"The fastest way to do anything is not to do it at all." -- Cary Millsap, Optimizing Oracle Performance.
 
"A designer knows he has achieved true elegance not when there is nothing left to add, but when there is nothing left to take away." -- Antoine de Saint-Exupéry
 
The simpler implementation has two tables and three indexes, two unique. The more complicated implementation has three tables and five indexes, four unique. The index on asso_countries_players.player_name (which should be a surrogate ID -- what happens if a player's name changes, like if they get married or legally change it, as Chad Ochocinco (nee Johnson) did?) must also be unique to enforce the 0..1 nature of the relationship between players and countries.
 
If the associative entity isn't required by the data model, then eliminate it. It's generally pretty trivial to transform a 0..1 relationship or 1..n relationship to an n..n relationship:
 
 
 
Add associative entity (and I'd question the need for a surrogate key there unless the relationship itself had attributes, like a start or end date)
 
 
Populate associative entity with existing data
 
 
Reimplement the foreign key constraints
 
 
Remove superseded foreign key column in child table.