Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index

On 07/24/2012 01:39 PM, Mark Stanton wrote:
In article <>, Jay Lozier wrote:
Actually most users of different backend db will be familiar with the
SQL version of that backend. What users need are two things: a connector
between Base and the backend and instructions on connecting to that backend.
The problem is, I think, that Base does some "pre-processing" to check the SQL, which
causes a problem, particularly in this context (non-standard SQL).  Although there are
some helpful points to it are there enough?

Another question is whether a generic connector versus a specific connector (say for MySQL) will more problematic. I would hope a specific connector would address using some of the extensions which a generic connector probably would not. Also, I would expect Base to lag behind the current release of most backends. New features in the current release may not be supported by Base or the connector. The severity of this issue probably depends on whether the db project/vendor explicitly supports using Base as a front end or are they supplied by others (independent or AOO/LO).

I prefer to use Base for entry forms and predefined queries and use other db specific tools for administrative tasks and db design.

Jay Lozier

For unsubscribe instructions e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.