Regina Henschel wrote:
Hello Frank,
Frank Schönheit - Sun Microsystems Germany schrieb:
FYI. As always, feedback is highly appreciated in
[EMAIL PROTECTED]
Ciao
Frank
-------- Original Message --------
Subject: Link CSV/Text files into HSQL databases / preliminary / 0.2
Date: Tue, 05 Sep 2006 15:52:01 +0200
From: Frank Schönheit <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: [email protected]
Title
=====
Link CSV/Text files into HSQL databases
Location
========
http://dba.openoffice.org/specifications/Link_CSV_Text_files_into_HSQL_databases.odt
I had a look at it. The new UI seems to focus on using existing
csv-files and it looks good for those cases. But why restrict it to
only existing csv-files?
I had transformed the biblio table in such a linked table and it was
very troublesome to do all the work with direct SQL. I would like to
see this additions:
In step "table" (1.3.1) allow to enter the name of a not existing
csv-file. OOo will generate that file then.
In step "table" (1.3.3) give the possibility to copy the column
definitions of an existing table out of the same database-document.
That would give you a simple workflow for exporting tables into
csv-format; direct in base, without Calc-detour and size limit of
Calc. In the new UI you would generate a new linked text table with a
new csv-file by copying the column definitions and then append the
records with the already existing paste dialog. That would not be one
command as requested in issue 58915 or issue 41556, but a step to a
solution.
kind regards
regina
I agree that having a simpler, meaning GUI based, way to convert a
standard table to a TEXT table, and therefore a text file would be
helpful. I wonder, would it make sense to go the same route of using
context menus for Tables and Queries as is used now for converting a
query to a view and a table to a form via the wizard. This would mean
adding the same context menu to both Tables and Queries, as exporting a
query is every bit as important as complete tables. Also, this function
would not just create the definition of the text table and the name of
the text file, but would also populate it with the records from the
originating object ( Table or Query or View ).
One concern I would have is that of raising confusion in the users mind.
If you offer a simple way to change a standard table to a text table,
and get a csv file as a result they might think that some link still
exists between the standard table and the finale text file. There is
none however.
I suppose I am going beyond Regina's main focus here however. Sticking
just to the 'Edit Linked Table' dialog. I would agree, at least to the
point of, that supporting the creation of a new text file should be
supported, not just linking to existing files.
Drew
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
