https://bugs.documentfoundation.org/show_bug.cgi?id=169954
Bug ID: 169954
Summary: Enhancement Request: CSV File Imports into BASE
Product: LibreOffice
Version: 25.8.3.2 release
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: enhancement
Priority: medium
Component: Base
Assignee: [email protected]
Reporter: [email protected]
Description:
Issue -- Tables created from CSV connections cannot be structurally modified.
If you need to add fields or create new tables, the CSV file has to be imported
into a new Base database instead. There is no warning when importing a CSV file
into Base that the resulting structure is READ ONLY.
The user experience is misleading. Base gives the impression that:
You “imported” a CSV
You now have a table
You can work with it like any other table
But in reality:
You created a connection, not a table
The structure is locked
The UI doesn’t warn you. The UI doesn’t explain the limitation. The UI
doesn’t guide you to the correct workflow.
I would recommend a warning or some sort of display that warns the user that if
they are just importing a CSV file - that the resulting DB tables will NOT be
editable and the resulting existing data CAN be edited - but you cannot add new
records. If you truly want the structure to be database-like - you MUST import
the csv data into an NEW database -- NOT use the import CSV routine which
renders the structure READ-ONLY. Additionally, there is no key field
identified in an import which essentially renders the existing data base
structure almost useless from any further refinement.
LibreOffice does give the impression that CSV import is seamless…and then
quietly hands you a “table” that isn’t a real table.
There’s no warning, no tooltip, no “by the way, this will be read‑only for
structure.” Just a silent assumption that the user understands the difference
between:
Connecting to a CSV (read‑only schema, editable data) vs.
Importing a CSV into a real Base database (fully editable)
That distinction is invisible unless you already know the architecture.
Steps to Reproduce:
1.Import a CSV file (let the software do the import -- not setting up a new DB
first)
2. Import the data
3. Try to add fields to the table or try to add a new table to the database (it
cannot be done)
Actual Results:
The resulting data in the tables that were generated can be edited; however,
you CANNOT add any new records. You also CANNOT add any new fields to the
tables. You also DO NOT have any key field identified in the new table(s).
Expected Results:
If you imported correctly -- the resulting DB structure SHOULD be editable.
And if this does not change, then a WARNING should be given that IF you want to
edit the new structure after a CSV import-- then using the CSV import WILL NOT
work for your workflow and you need to instead -- Setup a brand new DB
structure - and copy and paste the data into the new DB.
Reproducible: Always
User Profile Reset: No
Additional Info:
Give a warning or let people know that the resulting structure is a READ-ONLY
DB.
--
You are receiving this mail because:
You are the assignee for the bug.
