On 03/01/17 20:51, Vlad Khorsun wrote: > 01.03.2017 19:22, Dmitry Yemanov wrote: >>> 01.03.2017 19:50, Vlad Khorsun wrote: > .. >>> Also, I prefer to avoid to return as a string something that is not a >>> string. >> Agreed here. From another side, I don't like polluting the global >> namespace with non-standard but reserved keywords. > Same here. Therefore i offer such long names, to avoid possible clashes :) > So, what will be our decision ?
Vlad, what happens if user already had variable CURRENT_TRANSACTION_TIMESTAMP in his code? I ask cause this name has (as far as I can see in SQL 2008) nothing to do with SQL standard and someone might easily call his variable this way, ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
