To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=55884
------- Additional comments from [EMAIL PROTECTED] Thu Oct 13 23:35:21 -0700
2005 -------
well, this could be worked around by introducing something like
implExecuteQuery( String, XMetaData )
which is called from both Statement::executeQuery and
PreparedStatement::execute.
Alternatively, the Statement bass class could hold the meta data object, and
remember the statement it holds for. Then, every time a new result set is
created, for some given statement, it's checked whether this statement is the
same as for the previous result set. If yes, the old meta-data is re-used, if
no, a new instance is created.
Probably, a method like
XMetaData Statement::getResultSetMetaDataForStatement( String )
would do. It would be used in all places which currently access m_xMetaData
direcly (which would be forbidden then), and internally cache the meta data.
A class like (sketched only)
class MetaDataCache
{
private:
::rtl::OUString m_sPreviousStatement;
public:
MetaDataCache();
Reference< XMetaData >
getMetaDataForStatement( const ::rtl::OUString& _rCurrentStatement );
}
would probably be the ultimate decoupling then :)
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
