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

Sent to just Alex T by mistake:

On 1/15/14 1:41 PM, Carl Paulsen wrote:
OK, this is VERY helpful.

I decided to try reading the file in a text editor and that was instructive! The file is about 13MB, and from a quick read through, the vast majority seems to be actual data in a kind of comma-delimited form. First part seems to be instructions for setting up the tables including keys and fields/columns, etc. I don't pretend to understand a lot of it, but I think I get the basics.

So... Given it has instructions for table setup and raw data in it, how do I "open" it in LO? Or would I be better off moving to MySQL or something else and trying that? Is there usually info in the file about which db engine produced the file, or is there any other way to determine that?

Maybe I'll just see if I can open it directly in LO and hope for the best. If you have other thoughts, though, I'd be grateful to hear them.

Cheers again,

On 1/15/14 12:57 PM, Alex Thurgood wrote:
Le 15/01/2014 16:51, Carl Paulsen a écrit :

Hi Carl,

An SQL file does not necessarily need to contain "data", it could
contain just a set of instructions for the database engine to execute.

The SQL file is not a database as such, it is a generally text file
containing instructions that a SQL db engine will understand and
optionally data enclosed within INSERT statements.

If your SQL file contains both data and instructions, it would be a good
idea to know how it was produced, i.e. from which db engine the output
came, as SQL dialects between different vendors, db engines etc, can
differ according to their specific implementations of the SQL standards.

The file itself should be loadable into any text editor, providing that
it can handle the size of the file ! That can give you a better idea of
what's inside. For example, it is all very well having just insert
statements with associated data in a SQL file, but if the tables and db
haven't been set up in advance, you won't be able to get very far with it.

Some of those SQL statements might be directly executable from an empty
LO Base file in the Tools > SQL window, e.g. table creation statements,
key definition statements, constraints, etc, but again that would depend
on whether these statements were supported by the version of hsqldb that
comes with a default embedded ODB database file.



Carl Paulsen

Dover, NH 03820

To unsubscribe 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.