FS' API Incompatibility Wishlist
From Apache OpenOffice Wiki
That's just my personal list of UNO APIs I would like to change incompatibly, if we are ever allowed to. Note there's much more than this. I just can't remember at the moment, but when working with API, I regularily encounter things which now will hopefully appear here over time.
various
- XRowSetSupplier:
setRowSet
should be allowed to throw a NoSupportException - There should be an interface merging XRow and XResultSet. Both are nearly always used together, and having to work with two interfaces, one for navigating through the result set, and one for querying the actual values, sucks.
- XContent should have direct access to selected properties. Asking for a given property by executing a command named
getPropertyValues
, which returns aXRow
/XResultSet
, through which you need to navigate, is absolutely ridiculous. - various XDatabaseMetaData methods should take
any
s instead of strings. For instance, getTables should take anany
for the schemaPattern, whereNULL
indicates "all schemas", as in JDBC. - XPropertyContainer::addProperty should allow for
NULL
defaults, by separating between the type of a property, and its default.
Exception declarations
- XFilter::filter should be allowed to throw exceptions (
InvalidArgument
,InsufficentArguments
, or the like)