Den 2013-12-16 12:28 skrev Dimitry Sibiryakov såhär: > 16.12.2013 12:18, Alex Peshkoff wrote: >> On 12/16/13 15:14, Dimitry Sibiryakov wrote: >>> 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'); > But aren't fixed attributes also attributes? I don't really see where is > non-readability in syntax like this: > > create user x attributes (password = 'y', a = 'a', b = 'b'); > alter user x set password = 'yy', a = 'aa', b = 'bb'; > > Syntax diagram is the same as for UPDATE statement.
The problem as I see it is that unless you differentiate between standard/fixed attributes and user defined ones, you are going to build a mountain of future problems. When you want to introduce a new fixed attribute, X users will complain about clashes with their already-in-use user defined attributes. Separating them with some keyword (agreed that "attributes" is not optimal) will solve this and also make the syntax slightly clearer imho. Kjell -- -------------------------------------- Kjell Rilbe DataDIA AB E-post: kj...@datadia.se Telefon: 08-761 06 55 Mobil: 0733-44 24 64 ------------------------------------------------------------------------------ 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
