diff options
Diffstat (limited to 'offapi/com/sun/star/sdb')
5 files changed, 10 insertions, 10 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. diff --git a/offapi/com/sun/star/sdb/XSingleSelectQueryComposer.idl b/offapi/com/sun/star/sdb/XSingleSelectQueryComposer.idl index e5de0382d433..1674f4500531 100644 --- a/offapi/com/sun/star/sdb/XSingleSelectQueryComposer.idl +++ b/offapi/com/sun/star/sdb/XSingleSelectQueryComposer.idl @@ -190,7 +190,7 @@ interface XSingleSelectQueryComposer: XSingleSelectQueryAnalyzer not covered by the various set and get methods of the composer. That is, if the elementary statement contains a filter clause, a call to <member>XSingleSelectQueryAnalyzer::getFilter</member> will not return you this - filter. Instead, only filters which have been set using for instance <member>setFilter</member> + filter. Instead, only filters which have been set using for instance setFilter() are covered by the get methods.</p> <p>The only methods which take all parts of the elementary statement into account are @@ -200,7 +200,7 @@ interface XSingleSelectQueryComposer: XSingleSelectQueryAnalyzer <p>As a result, you can use the composer to build cumulative filter expressions. That is, you can set <member>ElementaryQuery</member> to a statement already containing - filters, and then use <member>setFilter</member> to append additional filters.</p> + filters, and then use setFilter() to append additional filters.</p> <p>The very same holds for sort orders, <code>HAVING</code> and <code>GROUP BY</code> clauses.</p> diff --git a/offapi/com/sun/star/sdb/application/CopyTableWizard.idl b/offapi/com/sun/star/sdb/application/CopyTableWizard.idl index 03c07a7bec9f..3cadfb51d250 100644 --- a/offapi/com/sun/star/sdb/application/CopyTableWizard.idl +++ b/offapi/com/sun/star/sdb/application/CopyTableWizard.idl @@ -52,7 +52,7 @@ module com { module sun { module star { module sdb { module application { </ul></p> <p>When you do not specify an interaction handler by using the - <member>createWithInteractionHandler</member> constructor, the wizard will use the interaction + createWithInteractionHandler() constructor, the wizard will use the interaction handler associated with the copy target, i.e. the interaction handler specified when loading the document which the copy target refers to. If the copy target cannot be associated with a database document (e.g. because it is a mere <code>ConnectionResource</code>, or a connection @@ -63,7 +63,7 @@ module com { module sun { module star { module sdb { module application { the copy source and the copy target descriptors are used to create a Connection. For any interaction during this phase - including, for instance, necessary authentication -, the interaction handler of the respective data source is used, no matter what you specified - in <member>createWithInteractionHandler</member>. Only if there is no such interaction + in createWithInteractionHandler(). Only if there is no such interaction handler, the processing described above, to find another handler, is applied.</p> </dd> @@ -173,7 +173,7 @@ service CopyTableWizard : XCopyTableWizard /** creates an executable wizard dialog, which is to guide the user through copying a table from one database to another. - <p>The only difference to the <member>create</member> constructor is that + <p>The only difference to the create() constructor is that <code>createWithInteractionHandler</code> takes an additional argument, which can be used to intercept interactions (such as error messages) during the wizard run.</p> diff --git a/offapi/com/sun/star/sdb/application/XDatabaseDocumentUI.idl b/offapi/com/sun/star/sdb/application/XDatabaseDocumentUI.idl index 7c1495f8c6c3..d4a95a6e978f 100644 --- a/offapi/com/sun/star/sdb/application/XDatabaseDocumentUI.idl +++ b/offapi/com/sun/star/sdb/application/XDatabaseDocumentUI.idl @@ -247,7 +247,7 @@ interface XDatabaseDocumentUI /** loads the given sub component of the database document - <p>In opposite to <member>loadComponent</member>, this method allows you to specify + <p>In opposite to loadComponent(), this method allows you to specify additional arguments which are passed to the to-be-loaded component.</p> <p>The meaning of the arguments is defined at the service which is effectively @@ -282,7 +282,7 @@ interface XDatabaseDocumentUI /** creates a new sub component of the given type - <p>In opposite to <member>createComponent</member>, this method allows you to specify + <p>In opposite to createComponent(), this method allows you to specify additional arguments which are passed to the to-be-loaded component.</p> <p>The meaning of the arguments is defined at the service which is effectively diff --git a/offapi/com/sun/star/sdb/tools/XObjectNames.idl b/offapi/com/sun/star/sdb/tools/XObjectNames.idl index 34777ad324bc..dafa0eeb7057 100644 --- a/offapi/com/sun/star/sdb/tools/XObjectNames.idl +++ b/offapi/com/sun/star/sdb/tools/XObjectNames.idl @@ -141,8 +141,8 @@ interface XObjectNames /** checks whether a given name is allowed for a to-be-created table or query in the database. - <p>This method basically does the same checks as <member>isNameUsed</member> and - <member>isNameValid</member>. In case the given name is not allowed, it throws an + <p>This method basically does the same checks as isNameUsed() and + isNameValid(). In case the given name is not allowed, it throws an exception. This error can be presented to the user, to give it a common experience in all cases where he's required to enter an object name.</p> |