Bug 67144 - EDITING: ODBC - Firebird: Could not input Integer-values
Summary: EDITING: ODBC - Firebird: Could not input Integer-values
Status: RESOLVED DUPLICATE of bug 45881
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
4.1.0.3 rc
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-21 20:00 UTC by Robert Großkopf
Modified: 2014-12-29 11:37 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
Failure-message when primarykey is integer in firebird, connected through ODBC (39.28 KB, image/png)
2013-12-16 15:43 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 2013-07-21 20:00:52 UTC
I try the connection between Firebird and LO..
When I try to add new data in an Integer-field the field will be NULL. No value would appear. So its impossible to put data into a table with an Integer primarykey.
When I try the same with Tools → SQL I could insert data into the table.

Here the odbcinst.ini for the connection:
[Firebird]
Description		= Firebird ODBC driver
Driver64		= /usr/lib64/libOdbcFb.so

Here the odbc.ini for the connection:
[Firebird-libretest]
Description 	= Firebird database libreoffice test
Driver          = Firebird
Dbname          = localhost:libretest.fdb
SensitiveIdentifier = Yes

(Without SensitiveIdentifier its impossible to put data into a table when there are lower letters in the tablename or in the fieldname)

I tested this with LO 4.1.0.3 on OpenSUSE 12.3 64bit rpm.
Comment 1 Robert Großkopf 2013-08-06 18:55:40 UTC
Could be the same bug as described here: https://bugs.freedesktop.org/show_bug.cgi?id=45881 ... don't know.
Comment 2 Robinson Tryon (qubit) 2013-12-16 04:33:38 UTC
(In reply to comment #1)
> Could be the same bug as described here:
> https://bugs.freedesktop.org/show_bug.cgi?id=45881 ... don't know.

Hi Robert,
Are you still seeing this problem with modern builds?  (e.g. 4.2.0.0.beta2)
Comment 3 Robert Großkopf 2013-12-16 15:43:34 UTC
Created attachment 90839 [details]
Failure-message when primarykey is integer in firebird, connected through ODBC

I have created a table for firebird with JDBC and LO. There is an Integer-field for the primary-key. Then I put values in the table through JDBC.
When I try the same with ODBC through the GUI an error occurs:
validation error for column ID, value "***null***".
When I try it with the same connection with Tools → SQL it works.
So this is an error produced from LO, not from ODBC.

It is the same error in all LO-versions, up to LO 4.3.alpha, also 4.2.0.0beta2.
Comment 4 Lionel Elie Mamane 2014-12-29 10:38:51 UTC
This smells like bug 45881; try with INT64 or SMALLINT instead of INTEGER.
Comment 5 Robert Großkopf 2014-12-29 10:57:47 UTC
(In reply to Lionel Elie Mamane from comment #4)
> This smells like bug 45881; try with INT64 or SMALLINT instead of INTEGER.

You are right, works with SMALLINT.
I could input values in this way, but it works with Integer-values through tools → SQL. 

If it works through Tools → SQL - isn't it a buggy behavior of LO?
Comment 6 Lionel Elie Mamane 2014-12-29 11:37:29 UTC
(In reply to robert from comment #5)
> (In reply to Lionel Elie Mamane from comment #4)
>> This smells like bug 45881; try with INT64 or SMALLINT instead of INTEGER.

> You are right, works with SMALLINT.
> I could input values in this way, but it works with Integer-values through
> tools → SQL. 

> If it works through Tools → SQL - isn't it a buggy behavior of LO?

It means it is a bug of something that sits between the user and Firebird. In the case of bug 45881, it is the ODBC driver. I think the best way to proceed is get bug 45881 fixed in the ODBC driver, and take it from there.

In the meantime, I'm marking this as a duplicate of bug 45881, since the fact that it is specific to INTEGER (and does not happen with SMALLINT) is a strong clue.

*** This bug has been marked as a duplicate of bug 45881 ***