To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=66576
------- Additional comments from [EMAIL PROTECTED] Tue Jun 20 00:27:51 -0700 2006 ------- Note: I'm not sure this service is a good idea. The semantics of substituteVariables doesn't seem to exactly match what is done here. Also, error conditions (e.g. an unparsable statement) cannot be reported, since the method is only allowed to throw an NoSuchElementException. May I suggest to instead e.g. enhance the query composer to allow for parameter substitution? This sounds like a more natural entry point to me. It would also overcome the problem that in fact the class cannot really provide its service in the current form: There's no way to specify a connection to be used, but parsing SQL statements does only make sense relative to a connection. Alternatively to the query composer, the newly introduced css.sdb.tools.XConnectionTools might be a good entry point for parameter substitution. --------------------------------------------------------------------- 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]
