I think that this would have 2 disadvantages from reader's perspective: * The same category will include useful pages, and pages describing syntaxes that are not available in the SQL_MODE he plans to use. This kind of defies the purpose of categorise pages.* Once found what he needs, he will have to read more contents to find out what is applicable for his case. What if some SQL_MODE=ORACLE pages would skip the discussion about semantics? For example, what if the page about 'Oracle WHILE' shows the syntax and a link to the 'Native WHILE' page? Would this make the pages maintainable enough? Federico Da: Sergei Golubchik <serg@mariadb.org> A: Alexander Barkov <bar@mariadb.org> Cc: Federico Razzoli <federico_raz@yahoo.it>; Maria Discuss <maria-discuss@lists.launchpad.net> Inviato: Lunedì 5 Marzo 2018 14:51 Oggetto: Re: [Maria-discuss] SQL_MODE=ORACLE documentation Hi, Alexander! On Mar 05, Alexander Barkov wrote:
For example, for the WHILE loop syntax, do we need an new PL/SQL article similar to https://mariadb.com/kb/en/library/while/ , or should we put the PL/SQL WHILE syntax directly on this page.
What do you think would be more readable?
I'm slightly inclined towards having separate pages for SQL/PSM and PL/SQL, with links to each other in the "See Also" section.
I think it'd be clearer to have them on the same page, as the semantics is mostly the same, only the syntax differs. Oracle mode syntax could be wrapped in something similar to <<product>> tags, so that it could be hidden when a user isn't interested in it. Duplicating every related page would introduce the documentation into the sql_yacc_ora.yy like mess. Regards, Sergei Chief Architect MariaDB and security@mariadb.org