To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=94543
User 400guy changed the following:
What |Old value |New value
================================================================================
Ever confirmed| |1
--------------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
--------------------------------------------------------------------------------
------- Additional comments from [email protected] Fri Mar 19 13:44:43
+0000 2010 -------
Conclusion: I recommend that this issue be confirmed.
I have managed to create situations very much like what I have noticed
in danros66's attachments. This happens with OS/400 V5R2 using
database and spreadsheet interfaces of a lightly hacked non-production
local build of DEV300_m75. As the results are consistent across OOo
interfaces, I am not providing quite the step-by-step instructions
that rainerbielefeld asked for above.
Database setup on AS/400
------------------------
I defined my test file with an SQL statement in member QALLSRC(AA6411)
create table aa6411 (
keyfield int not null primary key,
ts timestamp not null,
comment char(30)
);
invoked with CL statement
RUNSQLSTM SRCFILE(QALLSRC) SRCMBR(AA6411) COMMIT(*NONE)
I populated the thest file with SQL statments in member QALLSRC(AA6412)
delete from aa6411;
insert into aa6411 values( 1, '1990-03-02-08.30.00.100000',
'copied from V5R2 manual' );
insert into aa6411 values( 2, '2008-10-01-10.41.54.090000',
'danros66 got time 10:42' );
insert into aa6411 values( 3, '2008-10-01-10.41.52.305824',
'danros66 got time 10:51' );
insert into aa6411 values( 4, '2008-10-01-10.41.54.306208',
'danros66 got time 10:44' );
invoked with CL statment
RUNSQLSTM SRCFILE(QALLSRC)
SRCMBR(AA6412)
COMMIT(*NONE)
Using isql, part of DB2 on Linux, I retrieved the table, showing the
expected values
SQL> select * from aa6411
+------------+---------------------------+-------------------------------+
| KEYFIELD | TS | COMMENT |
+------------+---------------------------+-------------------------------+
| 1 | 1990-03-02 08:30:00.100000| copied from V5R2 manual |
| 2 | 2008-10-01 10:41:54.090000| danros66 got time 10:42 |
| 3 | 2008-10-01 10:41:52.305824| danros66 got time 10:51 |
| 4 | 2008-10-01 10:41:54.306208| danros66 got time 10:44 |
+------------+---------------------------+-------------------------------+
SQLRowCount returns -1
4 rows fetched
I have a prexisting ODBC connection defined to the AS/400.
Observations in OpenOffice
--------------------------
I created an OOo database using a previously defined ODBC connection.
In OOo Base SQL View, I created query "simplest" from SQL statement
select * from AA6411
which returns, give-or-take my typing mistakes, the incorrect values
that danros66 reported ...
KEYFIELD TS COMMENT
-------- -------------- ------------------------------
1 02/03/90 08:39 copied from V5R2 manual
2 01/10/08 10:42 danros66 got time 10:42
3 01/10/08 10:51 danras66 got time 10:51
4 01/10/08 10:44 danros66 got time 10:44
In Calc, I opened a new workbook, pressed F4, drilled down, and
dragged the query into the worksheet, getting the same incorrect
result. I shall attach the resulting workbook.
My local hacks to OpenOffice
----------------------------
(*) I have removed "typedef int BOOL;" from iodbcunix.h as it is in my
Ubunty Hardy installation and copied the result to
connectivity/inc/iodbcunix.h and dbaccess/inc/iodbcunix.h
(*) svl/source/misc/inettype.cxx incorporates sb's patch for issue
109146 and the unreferenced routine tje_20100316() quoted in
<http://www.openoffice.org/servlets/ReadMsg?list=dev&msgNo=26782>.
(*) From sw/source/filter/asc/parasc.cxx I have deleted lines 259 and
260, to avoid the assertion described in issue 109179.
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
