Bug 126645 - Firebird: AutoValue doesn't work with tablename and fieldname with special characters
Summary: Firebird: AutoValue doesn't work with tablename and fieldname with special ch...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
6.2.5.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-07-31 18:16 UTC by Robert Großkopf
Modified: 2019-07-31 18:32 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
Open the table and try to add a new value for field "Straße" (80.39 KB, application/vnd.oasis.opendocument.database)
2019-07-31 18:16 UTC, Robert Großkopf
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Großkopf 2019-07-31 18:16:41 UTC
Created attachment 153080 [details]
Open the table and try to add a new value for field "Straße"

Open the attached database.
Open the table "Straße".
Add a value for the field "Straße" and try to save.
Firebird ignores the autovalue and begins to count with the first value:
-----
firebird_sdbc error:
*violation of PRIMARY or UNIQUE KEY constraint "INTEG_6" on table "Straße"
*Problematic key value is ("ID" = 3)
caused by
'isc_dsql_execute'
-----
You have to try it again and the problematic key will count "ID"=4, "ID"=5 ...

have tested it with a normal table (Table named "table", field named "Name") and couldn't get this error. Think it must be an error, which only occurs with special characters in fieldname and/or tablename.
Comment 1 Robert Großkopf 2019-07-31 18:22:20 UTC
Have tried it with the same table after changing the tablename and the fieldname. Doesn't work. The same error.

This error appears after migrating a database from a HSQLDB-database to a Firebird-database.

Migrated with LO 6.3.0.1, opened for input data with LO 6.2.5.2 on OpenSUSE 15 64bit rpm Linux.
Comment 2 Robert Großkopf 2019-07-31 18:32:05 UTC
Have tried it again with converting the original HSQLDB-file in LO 6.3.0.2 - works now. Could be it has been converted sometimes before. Couldn't reproduce the error.