Thomas Hallgren wrote: > One might argue that it will prevent current PostgreSQL users from > unintentionally using those keywords and thereby obtain 2 goals: > > 1. The SQL code will be more portable since other databases may > recognize the keywords. > 2. Migration to a future PostgreSQL version where the relevant > commands has been implemented will be easier.
There is, however, little to no evidence that any other SQL implementation reserves those key words or that a future PostgreSQL feature addition would have to reserve them. Advising users of possibly unportable features is a valid goal, but it is best solved as part of the SQL flagger feature that prints out warnings for all extensions, not just some key words. Various discussions about the SQL flagger are in the archive. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
