-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > P.S. The use of capital "s" is possible a source of some of the resistance. It > seems like a lowercase "s" or something else that doesn't need multiple > keystrokes would be a lot easier to type. Is there some limitation on the > \command parser that makes \dfs harder? Not in the parser, per se, but I presume that "S" was chosen becuase "s" was already taken by sequences, e.g. \ds and \dS already have different behaviors, and since the order of the letters after the \d does not really matter, there needed to be a way to let \dSt work. All presumptions on my part, there may be some more historical reasons. I don't think a capital S is too much work myself... :) - -- Greg Sabino Mullane greg@xxxxxxxxxxxx PGP Key: 0x14964AC8 200506181059 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iD8DBQFCtDbJvJuQZxSWSsgRAutQAJ4/1UWWQ1awKg+ucvY35rLQKHsRsACfY+kM t5zaT59WY02+DU2G9MR18zY= =9Dmn -----END PGP SIGNATURE----- ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
