<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_UNCONFIRMED "
title="UNCONFIRMED - In query editor add a switch to turn off the query interpreter (syntax checker) without disabling GUI query editing"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=112801">112801</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>In query editor add a switch to turn off the query interpreter (syntax checker) without disabling GUI query editing
</td>
</tr>
<tr>
<th>Product</th>
<td>LibreOffice
</td>
</tr>
<tr>
<th>Version</th>
<td>5.3.3.2 release
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>UNCONFIRMED
</td>
</tr>
<tr>
<th>Severity</th>
<td>enhancement
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>Base
</td>
</tr>
<tr>
<th>Assignee</th>
<td>libreoffice-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>BridgeportContractor@gmail.com
</td>
</tr></table>
<p>
<div>
<pre>Currently when connecting to any non-built-in database, such as Mariadb, MySQL,
etc, the graphical query editor is only usable for simple queries, with simple
SQL.
For example, if you try to use "AND" to test two conditionals you get: "syntax
error". See:
<a href="https://ask.libreoffice.org/en/question/133467/base-andor-syntax-w-mysql/">https://ask.libreoffice.org/en/question/133467/base-andor-syntax-w-mysql/</a>
The only workaround is to turn off the query interpretor (for how, see link
above) and this allows your SQL to pass directly to MariaDB, but at the cost of
disabling the powerful LO GUI query editor.
Now you're back to writing plain old SQL text but with no join diagrams. :-(
Problem summary: The LO SQL interpreter must be able to read SQL text so as to
produce the GUI view.
ENHANCEMENT SUGGESTION:
For the GUI editor to work with all SQL varieties, I think what is needed is a
smarter SQL parser (or you might say a dumber one), one that parses just enough
of the SQL to produce the GUI, but not so much as to limit enhanced SQL
features.
In other words, it needs to be able to parse the SELECT, then break apart the
comma joined field descriptions (but without full forward parsing), then find
the FROM, and proceed as before. This would allow the GUI to work with complex
SQL.
Parser:
1) Look for SELECT,
2) then look for select fields descriptors (delimited by an un-bracketed comma
(i.e. not inside (), '', or ``, etc.),
3) until FROM is found, then proceed as before.
I think this should be a rather simple parser, but of course no parser is
trivial.
For the future I think this would be an important Base improvement and help
keep LO flexible and allowing users to better connect to a wide variety of
databases.
I assume this is a pretty big challenge, so will manage my hopes of it coming
soon.
Thanks.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>