Issue 84235 - runner: dbaccess.ORowSet::com::sun::star::sdbc::XWarningSupplier
Summary: runner: dbaccess.ORowSet::com::sun::star::sdbc::XWarningSupplier
Status: CONFIRMED
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: All All
: P3 Trivial
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-04 15:07 UTC by chne
Modified: 2013-02-24 21:06 UTC (History)
1 user (show)

See Also:
Issue Type: TASK
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 chne 2007-12-04 15:07:41 UTC 
migrated from internal task:
	This interface annot really be tested. It should report warnings from the
database, but unfortunately our database connections (dbf, jdbc) do not get any
warnings that this interface can report.
So, to test this, a database connection that delivers warnings has to be found,
or it has to be implemented.
This is a difficult task for the test of an interface of little meaning.

The interface is also implemented by forms.ODatabaseForm.

FS->SG: Nowadays, warnings are implemented: If you open a HSQLDB database which
contains a table and a query with the same name, a warning will be issued, when
you connect to this DB. Such a database could be created by creating a query,
and then issueing a CREATE TABLE statement, creating a table with the same name.
Then disconnect and connect again, this will raise the warning.
Comment 1 chne 2007-12-13 22:34:16 UTC 
accepted
Comment 2 chne 2009-04-20 09:24:59 UTC 
change owner