no ORDER BY in selects?
2003-02-03 22:27:20 GMT
Is there a reason that the "get*Nodes" methods in, e.g. NetworkElementFactory don't do SELECTs with ORDER BY using some human-identifiable field, like nodeLabel? A lot of the screens come up with nodes listed in effectively random order (order of database select which is more or less undefined but correlates vaguely to "the order in which nodes were discovered or changes made to that node's fields") and makes it really hard to find a specific node if you're browsing through, for example, the "manage/unmanage" screen on the admin section. Adding ORDER BY NODELABEL would make many screens a lot more coherent. I can't think of a single reason NOT to add this, except if you WANT to see the nodes in roughly-discovery-or-last-modification order. You'd have to hanve thousands and thousands of nodes in the database for this to have any significant impact on performance, and even then, it would be minor compared to the number of connection setups/teardowns the current database model is using to retrieve a lot of data from the database. -- -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- #!/usr/bin/perl -w $_='while(read+STDIN,$_,2048){$a=29;$b=73;$c=142;$t=255; <at> t=map {$_%16or$t^=$c^=($m=(11,10,116,100,11,122,20,100)[$_/16%8])&110; $t^=(72, <at> z=(64,72,$a^=12*($_%16-2?0:$m&17)),$b^=$_%64?12:0, <at> z) [$_%8]}(16..271);if(( <at> a=unx"C*",$_)[20]&48){$h=5;$_=unxb24,join "", <at> b=map{xB8,unxb8,chr($_^$a[--$h+84])} <at> ARGV;s/...$/1$&/;$d= unxV,xb25,$_;$e=256|(ord$b[4])<<9|ord$b[3];$d=$d>>8^($f=$t&($d(Continue reading)
RSS Feed