Just for thinking... Can we create dialect 4 without old and strange things from sql standard? Strange things are: - inconsistances in naming such as CURRENT_TIMESTAMP and LOCALTIMESTAMP - 'ABC' = 'ABC ' -- ignored trailing spaces in varchars coparison (so we can't have 'ABC' and 'ABC ' in a field with unique constraint) - 2 / 3 = 0 - system functions are in global space. What if user has function or domain named LOCALTIMESTAMP? System functions can be prefixed (like SYS.LOCALTIMESTAMP). System tables can be in SYS namespace too (like SYS.RELATIONS, SYS.FIELDS). - all other known strange things
Dialect 3 can stay conformant to standard. But I think that most users will choose dialect 4 :) On 02.05.2018 17:26 Adriano wrote: > On 02/05/2018 05:59, Stefan Heymann wrote: >> Adriano, >>> Also there are new expressions, LOCALTIME and LOCALTIMESTAMP with >>> functionality equivalent to the Firebird's CURRENT_TIME and >>> CURRENT_TIMESTAMP. >> I'd like to suggest you name these LOCAL_TIME and LOCAL_TIMESTAMP (with >> the underscore in the middle) to make them look more like their >> CURRENT_xxx siblings. > Sorry but no, as the names comes from the standard. > Adriano ------------------------------------------------------------------------------ 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
