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
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?
Glad to hear that the plan is writing a detailed documentation. I'll probably
contribute as I did in the past, but I definitely don't have the time to find
out the correct syntaxes myself.
Yes, separate pages with links (where applicable) should be clear. IMHO,
putting everything in the same pag
IMHO, putting pointers each others will help instead of putting Oracle
Syntax in the mainline pages. This may cause confusion for the people who
never used oracle in firsthand.
On Mon, Mar 5, 2018 at 2:11 PM, Alexander Barkov wrote:
> Hello Federico,
>
> On 03/02/2018 07:12 PM, Federico Razzoli
Hello Federico,
On 03/02/2018 07:12 PM, Federico Razzoli wrote:
With SQL_MODE='ORACLE' a completely new syntax has been introduced.
Basic syntax constructs of MariaDB become unavailable, but not all
Oracle syntax seems to be supported. Is there any plan to document the
supported syntax? Curren
5 matches
Mail list logo
