To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=55884 Issue #:|55884 Summary:|[dev] clean up resultset/statement/metadata |relationship in various SDBC drivers Component:|Database access Version:|680m130 Platform:|All URL:| OS/Version:|All Status:|NEW Status whiteboard:| Keywords:| Resolution:| Issue type:|DEFECT Priority:|P4 Subcomponent:|none Assigned to:|oj Reported by:|fs
------- Additional comments from [EMAIL PROTECTED] Wed Oct 12 23:28:24 -0700 2005 ------- During discussing implementation issues for the KAdressBook SDBC driver, Éric Bischoff ([EMAIL PROTECTED]) pointed out that there's a suboptimal usage of result set meta instances, created by prepared statements and result sets, in various SDBC drivers. That is, a prepared statement can be asked for a ResultSetMetaData instance, which describes the result set which would be generated when the statement is executed. This is usually implemented by the PreparedStatement implementation having an own instance of a ResultSetMetaData implementation, which is constructed when needed. Additionally, the ResultSet created by the prepared statement can also provide a ResultSetMetaData instance. Since the meta data should be te same for both the statement and the result set (note that this is *by definition* of the getMetaData method of a PreparedStatement!), this could be optimized so that both the PreparedStatement and the ResultSet implemented by it use the same meta data instance. As an example for this, look at OResultSet::getMetaData and OPreparedStatement::getMetaData in connectivity/source/drivers/file, which pretty much duplicate the meta data code. --------------------------------------------------------------------- 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]
