On 07/24/2012 03:06 AM, Tom Davies 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.
If only it were possible to somehow communicate with people from the various back-end projects
perhaps even ask them to write-up a brief sub-chapter on how to use their back-end in conjunction
with Base. I wonder if any of them know anything about the use of Sql in their projects.
The BoD want to sit&wait rather than be pro-active about this sort of collaboration.
SQL is the standard query language for relational databases so if one
writes queries for a relational database one should know a dialect of
SQL. SQL has a published international standard that db developers
follow. The problem is that each developer will add non-standard
extensions for their db making the resulting code possibly not portable.
An example is loading/exporting data from a file into a database is
defined in the SQL specifications so each db has its extension to do the
same thing. Each extension needs the same information but has a
different syntax for the command.
--- On Mon, 23/7/12, Dan <firstname.lastname@example.org> wrote:
From: Dan <email@example.com>
Subject: Re: [libreoffice-users] Re: Re: SQL statement in Base query
Date: Monday, 23 July, 2012, 22:54
Ferry Toth wrote:
Did you try with another database as a backend? I like postgres as a
backend a lot.
I am writing a chapter of the Base Guide that includes using SQL
in the Query Design dialog. Chapter 8 of the Base Guides covers using
HSQLDB 2.2.8, MySQL, and PostgreSQL as back ends. So, I am not there
quite yet. It seems that because Base uses HSQLDB 1.8, it does not
conform with the user guide for the database engine it uses.
When I get to that point, I will need to research how each of
these backends use SQL.
Dan schreef op wo 18-07-2012 om 16:40 [-0400]:
Andreas Säger wrote:
On this simple level I would consider HSQLDB as free of bugs whereas the
primitive Base parser fails in many different ways.
Did you try the direct SQL mode (SQL view, menu:Edit>Run SQL directly)? If
you get reasonable result in direct mode, it is one of many bugs in the
Base's SQL parser.
View this message in context:
Sent from the Users mailing list archive at Nabble.com.
That is the one thing that I forgot to mention: I get the same
message when using direct SQL mode. I even tried using Tools > SQL, but
with the same message.
For unsubscribe instructions e-mail to: firstname.lastname@example.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Impressum (Legal Info)
: 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