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. Alex -- To unsubscribe e-mail to: [email protected] Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ 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
