Bug 124759 - ODBC - DB2 database access - First row missing from Base query results.
Summary: ODBC - DB2 database access - First row missing from Base query results.
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
6.2.2.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Database-Connectivity
  Show dependency treegraph
 
Reported: 2019-04-15 17:36 UTC by kovacs.zsolt.sandor
Modified: 2019-08-21 09:53 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 kovacs.zsolt.sandor 2019-04-15 17:36:51 UTC
Description:
First row missing from Base query results.

Steps to Reproduce:
1.Write query
2.Run
3.Missing first row
4.Refresh
5.Wow, happy

Actual Results:
Missing first row.

Expected Results:
With refresh is good.


Reproducible: Always


User Profile Reset: Yes



Additional Info:
[Information automatically included from LibreOffice]
Locale: hu
Module: QueryDesign
[Information guessed from browser]
OS: Windows 10
OS is 64bit: yes
Comment 1 Alex Thurgood 2019-04-17 07:50:21 UTC
@Sandor : what are you using as your datasource ?

Ideally, we need a sample database file where the problem occurs so that we can compare and try to reproduce.

Setting NEEDINFO.
Comment 2 kovacs.zsolt.sandor 2019-04-17 10:02:28 UTC
(In reply to Alex Thurgood from comment #1)
> @Sandor : what are you using as your datasource ?
> 
> Ideally, we need a sample database file where the problem occurs so that we
> can compare and try to reproduce.
> 
> Setting NEEDINFO.

I can't present that database.

Data source:
Client Access ODBC Driver (32-bit) 12.00.00.00 IBM Corporation
iSeries Access ODBC Driver
C:\WINDOWS\system32\cwbodbc.dll 2007.12.11

SQL::
select SYS_CNAME
from QSYS2.SYSCOLUMNS              
where SYS_TNAME='SYSTABLES'  
  and SYS_DNAME='QSYS2'      
  and SYS_CNAME < 'E'  
order by 1

Run(F5)::
SYS_CNAME
COLCOUNT  
CREATOR   
DBNAME    
DECFLTRND 
DEFINER   

Refresh::
SYS_CNAME
ALTEREDTS 
COLCOUNT  
CREATOR   
DBNAME    
DECFLTRND 
DEFINER   



With another data source, SQL server ( 10.00.17134.01 MS SQLSRV32.DLL 2018.04.12), work fine.
Comment 3 Alex Thurgood 2019-04-17 11:13:17 UTC
@Sandor : the driver you mention is specific for an ODBC connection to IBM DB2 databases

Why are you using the 32bit driver, instead of the 64bit driver, on your Win10 64bit OS ?

Changed title to reflect information provided.
Comment 4 Alex Thurgood 2019-04-17 11:24:51 UTC
Unfortunately, I do not have access to such a db setup, so can't test.

According to :

http://www-01.ibm.com/support/docview.wss?uid=nas8N1015102

the ODBC driver includes both 64 bit and 32 bit support built-in, and uses the bit type corresponding to the application which calls the driver.

However, this document also notes that the 64 bit driver is located in \windows\system32\cwbodbc.dll

So, despite the information you gave, indicating that the driver is 32bit, it is fact, at least according to IBM's own documentation, the 64-bit driver.

Go figure. Please ignore my questions, setting back to UNCONFIRMED
Comment 5 Xisco Faulí 2019-07-09 14:23:58 UTC
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
Comment 6 kovacs.zsolt.sandor 2019-07-10 05:44:02 UTC
(In reply to Xisco Faulí from comment #5)
> Could you please try to reproduce it with the latest version of LibreOffice
> from https://www.libreoffice.org/download/libreoffice-fresh/ ?
> I have set the bug's status to 'NEEDINFO'. Please change it back to
> 'UNCONFIRMED' if the bug is still present in the latest version.

Unfortunately, the problem still exists in the new version.
Comment 7 QA Administrators 2019-07-11 02:55:46 UTC Comment hidden (obsolete)
Comment 8 kovacs.zsolt.sandor 2019-08-21 06:48:32 UTC
Thanks to everyone for your efforts.

I had to reinstall my machine, which also solved this problem. Now it works fine.
Comment 9 Xisco Faulí 2019-08-21 09:53:02 UTC
Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.