summaryrefslogtreecommitdiff
path: root/offapi/com/sun/star/sdb/XSingleSelectQueryAnalyzer.idl
diff options
context:
space:
mode:
Diffstat (limited to 'offapi/com/sun/star/sdb/XSingleSelectQueryAnalyzer.idl')
-rw-r--r--offapi/com/sun/star/sdb/XSingleSelectQueryAnalyzer.idl2
1 files changed, 1 insertions, 1 deletions
diff --git a/offapi/com/sun/star/sdb/XSingleSelectQueryAnalyzer.idl b/offapi/com/sun/star/sdb/XSingleSelectQueryAnalyzer.idl
index b54eb937183e..bc9f8470f568 100644
--- a/offapi/com/sun/star/sdb/XSingleSelectQueryAnalyzer.idl
+++ b/offapi/com/sun/star/sdb/XSingleSelectQueryAnalyzer.idl
@@ -175,7 +175,7 @@ interface XSingleSelectQueryAnalyzer : com::sun::star::uno::XInterface
if the query represented cannot be completely substituted. A usual case for this is a recursion in
the sub queries: Consider a query named <code>foo</code>, which is defined as <code>SELECT * FROM "bar"</code>.
Now assume that <code>bar</code> is a query defined as <code>SELECT * FROM "foo"</code>. Passing either
- of those statements to an analyzer, and calling <member>getQueryWithSubstitution</member>, would result
+ of those statements to an analyzer, and calling getQueryWithSubstitution(), would result
in an exception being thrown, since it's impossible to substitute the sub queries with their
constituting statements.