Issue 97861 - checkapi -o dbaccess.ORowSet::com::sun::star::sdbcx::XDeleteRows fails for method deleteRows
Summary: checkapi -o dbaccess.ORowSet::com::sun::star::sdbcx::XDeleteRows fails for me...
Status: CLOSED FIXED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: DEV300m38
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: OOo 3.1
Assignee: marc.neumann
QA Contact: issues@dba
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2009-01-08 10:44 UTC by Frank Schönheit
Modified: 2010-02-22 14:42 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Frank Schönheit 2009-01-08 10:44:00 UTC 
This happens on unxlngi6.pro only, not on wntmsci12.

Running the XDeleteRows test for the row set fails for method deleteRows. To
reproduce:
- start OOo with "-accept=pipe,name=<userid>;urp"
- run checkapi -o dbaccess.ORowSet::com::sun::star::sdbcx::XDeleteRows
=> notice the log:

LOG> out > checking : _XDeleteRows
LOG> out > LOG> Execute: deleteRows()
LOG> out > LOG> Rows before: 0, after: 0
LOG> out > Method deleteRows() finished with state FAILED
LOG> out > LOG> deleteRows(): PASSED.FAILED
Comment 1 Frank Schönheit 2009-01-08 10:44:36 UTC 
That's a regression between m37 and m38, probably caused by either dba31d or dba31f.
Comment 2 ocke.janssen 2009-01-16 09:20:07 UTC 
Fixed in cws dba31h.
For the reason look at issue 97860
Comment 3 ocke.janssen 2009-01-26 07:22:17 UTC 
Please verify. Thanks.
Comment 4 marc.neumann 2009-01-26 14:27:47 UTC 
verified in CWS dba31h

find more information about this CWS, like when it is available in the master
builds, in EIS, the Environment Information System:
http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=DEV300%2Fdba31h
Comment 5 thorsten.ziehm 2010-02-22 14:42:12 UTC 
This issue is closed automatically. It should be fixed in a version with is
available for longer than half a year (OOo 3.1). If you think this issue isn't
fixed in the current version (OOo 3.2) please reopen it. But then please pay
attention about the field 'target milestone'.
The closure was approved by the Release Status Meeting at 22nd of February 2010
and it is based on the issue handling guideline for fixed/verified issues  : 
http://wiki.services.openoffice.org/wiki/Handle_fixed_verified_issues