Bug 130243 - EDITING Incorrect field name transfer from certain database columns on Windows
Summary: EDITING Incorrect field name transfer from certain database columns on Windows
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
6.2.8.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-28 15:45 UTC by Jochen Plumeyer
Modified: 2020-08-28 04:04 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jochen Plumeyer 2020-01-28 15:45:14 UTC
We tried on both current official Windows Versions (6.2.8, 6.3.4) of LibreOffice to transfer a database column name as a data field ("MwSt" by the way) from PostgreSQL. It always brought up a wrong field name "MWSt" with upper case "W".

None of the 3 Linux versions of LibreOffice (5.2 Debian, 6.2 and 6.3) had this problem.

Of course this lead to wrong output, as some default value is chosen then.

Perhaps relevant: The ODT had been created in OpenOffice-3.2 and contained somewhere perhaps the wrong field name, and OpenOffice did not seem to be restrictive about the case of field names.
Comment 1 Julien Nabet 2020-01-29 08:16:59 UTC
Do you reproduce this with a brand new odb file from 6.3.4?
Also, what's the type of connection? odbc, native postgresql ?

Would it be possible you provide SQL to generate structure of table?
If in Postgresql table you create a table with just one column called "MwSt" and copy paste it on odb file, do you reproduce the problem?
(the goal is to know if it's specific to a table or for any table)
Comment 2 QA Administrators 2020-07-28 04:47:38 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2020-08-28 04:04:09 UTC
Dear Jochen Plumeyer,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp