Issue 58882 - Use the spreadsheet data in right way, not just (incorrectly) guess the type
Summary: Use the spreadsheet data in right way, not just (incorrectly) guess the type
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 2.0
Hardware: All All
: P3 Trivial with 4 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Blocks: 35178
  Show dependency tree
Reported: 2005-12-05 11:34 UTC by tuharsky
Modified: 2013-02-07 22:41 UTC (History)
2 users (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---

The test case (6.01 KB, application/vnd.sun.xml.calc)
2005-12-05 11:35 UTC, tuharsky
no flags Details
Screenshot (94.86 KB, image/png)
2005-12-05 11:35 UTC, tuharsky
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description tuharsky 2005-12-05 11:34:36 UTC
Attached spreadsheet has 2 colums: Street and No.
If used as datasource, the street numbers with letters in them aren't displayed.
If MailMerge is done, the affected data are not merged (thus they are lost in
output or print). The behaviour probably cannot be affected by regular actions
of ordinary user, if it can be affected either.

I've formatted all cells as Text, and then the Column Format was set to Text too
in data view. (F4 key in word processor)

The database layer should
1. Either verify the real data type from each cell's format settings
2. Or allow user to set them manually
3. Both:
First step -try to guess the type by scanning the cells for each column.
Second step -allow user to change it, with DB Source View open so that he can
see, what he get

1. Don't know if it affects all databases or just Calc spreadsheets source
2. May be related to

3. Although for me it seems like bug and for sure it leads to unexpected loss of
data (P2), the developer 'clu' insists that this is an enhancement. So I'm
reporting this as enhancement.
Comment 1 tuharsky 2005-12-05 11:35:03 UTC
Created attachment 32050 [details]
The test case
Comment 2 tuharsky 2005-12-05 11:35:48 UTC
Created attachment 32051 [details]
Comment 3 marc.neumann 2005-12-05 12:10:23 UTC

I reassign this enhancement to the User Experience team for evaluating.

Bye Marc
Comment 4 martinkozak 2006-02-06 13:15:47 UTC
Lowering priority. Why P2?
Comment 5 tuharsky 2006-02-06 13:39:04 UTC
Because the user faces unexpected data loss.

"User data is corrupted in an easy-to-encounter way;
e.g. saving a document corrupts the resulting file and renders it unusable"