On 05/03/16 13:32, Dimitry Sibiryakov wrote: > Currently parser enforce attribute clauses to have a definite positions in > the > statement. SQL standard doesn't require that. > Do you agree that position-insensitive clauses would be more convenient?
It would be nice if we did not have re-order scripts from other databases so NOT NULL DEFAULT '30' has to be DEFAULT '30' NOT NULL in Firebird. I don't think that the SQL standard ever imposed an order on these? But both MySQL and Postgresql seem to standardise on the DEFAULT last :( It's a little less of a problem these days where an abstraction of some sort is used. ADOdb we can ensure the 'datadict' or 'XML' scripts produce the right order, but where initialise scripts use raw SQL it's a difficult one to modify on the fly. -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk ------------------------------------------------------------------------------ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
