On Tue, Jan 14, 2003 at 12:42:18AM +0200, Jani Tolonen wrote: ... > * Added join operator `FORCE INDEX (key_list)'. This acts likes `USE > INDEX (key_list)' but with the addition that a table scan is > assumed to be VERY expensive. One bad thing with this is that it > makes `FORCE' a reserved word.
Would it be possible then to choose a naming convention for MySQL extensions that is less likely to cause a conflict? Something like "__FORCE", "FORCE_INDEX", or even "MYSQL_FORCE" (or "MYSQL(FORCE)")? (Assuming FORCE this isn't standard SQL.) You could then add new extensions without worrying about breaking existing programs. I had to change a lot of code when "WHEN" became a reserved word (it makes a good name for a timestamp-type field), and it wasn't pleasant. (Though that in that 'case' it was a standard sql reserved word iirc.) I don't have any fields named "force", but surely someone does. Just a thought. Thanks for the great "sql, database" :) --Pete --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
