On 12/16/13 15:14, Dimitry Sibiryakov wrote: > 16.12.2013 12:08, Alex Peshkoff wrote: >> On 12/16/13 14:50, Dimitry Sibiryakov wrote: >>>> IMHO, for syntax consistency "set" should be placed before all >>>> changing parameters. >>>> I.e. if password identifies user record to be changed, "set" after it is >>>> ok, but if >>>> password is a subject to change, "set" should be before it. >>>> >> Please suggest a reasonable separator between fixed and optional >> properties in a case when set goes right after alter. > Why one is needed? You can tell whether it is fixed or optional property > by name, can't > you?.. > To make SQL operator human-readable. And must say I like this suggestion
create user x password 'y' attributes (a = 'a', b = 'b'); alter user x set password 'yy' attributes (a = 'aa', b = 'bb'); May be besides word "attributes" - some better replacement is desired on my mind. ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
