> So for a bit of useless syntactic sugar we should introduce conflicts with > named parameters, conflicts with operators, introduce an un-sqlish syntax and > remove a feature users have already made use of and introduce backwards > compatibility issues for those users? > we talk only about "=>" symbol. What I googled, I never to find any database that use AS for named params, and I don't really to create next proprietary syntax (I would not to wait to ANSI). AS is usable, but I don't think so it is good idea - it change sense of AS keyword in SQL.
Oracle: fce (param => expr) MSSQL: fce @param = expr Firebird 2.0 allows defaults, but doesn't support named params > At any point in this discussion has anyone explained why these labels would > actually be a good idea? > it's allows smart libraries like SQL/XML regards Pavel Stehule > -- > Gregory Stark > EnterpriseDB http://www.enterprisedb.com > Ask me about EnterpriseDB's 24x7 Postgres support! > -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
