From 5c82eb12e524d454c02798994d08d50548c9734c Mon Sep 17 00:00:00 2001 From: Olivier Hallot Date: Sat, 14 May 2022 12:39:47 -0300 Subject: Fix bad filename and links in Query Desing Help page + Remove internal links that breaks reading comfort. Change-Id: Ic417bfa2dd8f2b904575d69e6d3e98f0b8a8ce37 Reviewed-on: https://gerrit.libreoffice.org/c/help/+/134324 Tested-by: Jenkins Reviewed-by: Olivier Hallot --- source/text/sdatabase/02010100.xhp | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) (limited to 'source') diff --git a/source/text/sdatabase/02010100.xhp b/source/text/sdatabase/02010100.xhp index 0e6cd9e996..85233468ad 100644 --- a/source/text/sdatabase/02010100.xhp +++ b/source/text/sdatabase/02010100.xhp @@ -21,7 +21,7 @@ Query Design - /text/sdatabase/020010100.xhp + /text/sdatabase/02010100.xhp @@ -49,7 +49,7 @@ mw added "(Base)" to all entries -

Query Design

+

Query Design

The Query Design View allows you to create and edit a database query.
@@ -61,7 +61,7 @@

The Design View

To create a query, click the Queries icon in a database document, then click Create Query in Design View. -The lower pane of the Design View is where you define the query. To define a query, specify the database field names to include and the criteria for displaying the fields. To rearrange the columns in the lower pane of the Design View, drag a column header to a new location, or select the column and press Command +The lower pane of the Design View is where you define the query. To define a query, specify the database field names to include and the criteria for displaying the fields. To rearrange the columns in the lower pane of the Design View, drag a column header to a new location, or select the column and press Command Ctrl+arrow key. In the top of the query Design View window, the icons of the Query Design Bar and the Design bar are displayed. If you want to test a query, double-click the query name in the database document. The query result is displayed in a table similar to the Data Source View. Note: the table displayed is only temporary. @@ -185,7 +185,7 @@

Criteria

-Specifies a first criteria by which the content of the data field is to be filtered. +Specifies a first criteria by which the content of the data field is to be filtered.

or

Here you can enter one additional filter criterion for each line. Multiple criteria in a single column will be interpreted as boolean OR. @@ -814,9 +814,9 @@

Parameter queries

Parameter queries allow the user to input values at run-time. These values are used within the criteria for selecting the records to be displayed. Each such value has a parameter name associated with it, which is used to prompt the user when the query is run. Parameter names are preceded by a colon in both the Design and SQL views of a query. This can be used wherever a value can appear. If the same value is to appear more than once in the query, the same parameter name is used. -In the simplest case, where the user enters a value which is matched for equality, the parameter name with its preceding colon is simply entered in the Criterion row. In SQL mode this should be typed as WHERE "Field" = :Parameter_name +In the simplest case, where the user enters a value which is matched for equality, the parameter name with its preceding colon is simply entered in the Criterion row. In SQL mode this should be typed as WHERE "Field" = :Parameter_name Parameter names may not contain any of the characters <space>`!"$%^*()+={}[]@'~#<>?/,. They may not be the same as field names or SQL reserved words. They may be the same as aliases. -A useful construction for selecting records based on parts of a text field's content is to add a hidden column with "LIKE '%' || :Part_of_field || '%'" as the criterion. This will select records with an exact match. If a case-insensitive test is wanted, one solution is to use LOWER (Field_Name) as the field and LIKE LOWER ( '%' || :Part_of_field || '%' ) as the criterion. Note that the spaces in the criterion are important; if they are left out the SQL parser interprets the entire criterion as a string to be matched. In SQL mode this should be typed as LOWER ( "Field_Name" ) LIKE LOWER ( '%' || :Part_of_field || '%' ). +A useful construction for selecting records based on parts of a text field's content is to add a hidden column with "LIKE '%' || :Part_of_field || '%'" as the criterion. This will select records with an exact match. If a case-insensitive test is wanted, one solution is to use LOWER (Field_Name) as the field and LIKE LOWER ( '%' || :Part_of_field || '%' ) as the criterion. Note that the spaces in the criterion are important; if they are left out the SQL parser interprets the entire criterion as a string to be matched. In SQL mode this should be typed as LOWER ( "Field_Name" ) LIKE LOWER ( '%' || :Part_of_field || '%' ). Parameter queries may be used as the data source for subforms, to allow the user to restrict the displayed records.

Parameter Input

@@ -833,5 +833,4 @@ By clicking the Run SQL command directly icon in the SQL view, you can formulate a query that is not processed by $[officename] and sent directly to the database engine.
- -- cgit