Translation

02010100.xhp par_id191120151905518123 help.text
English f2NMg
Context English Dzongkha Actions
02010100.xhp
par_id3147481
help.text
Query criterion
02010100.xhp
par_id3155187
help.text
Example
02010100.xhp
par_id3156092
help.text
Yes
02010100.xhp
par_id3152414
help.text
for dBASE tables: not equal to any given value
02010100.xhp
par_id3151265
help.text
=1 returns all records where the Yes/No field has the status "Yes" or "On" (selected in black),
02010100.xhp
par_id3152450
help.text
No
02010100.xhp
par_id3150997
help.text
.
02010100.xhp
par_id3155331
help.text
=0 returns all records for which the Yes/No field has the status "No" or "Off" (no selection).
02010100.xhp
par_id3154179
help.text
Null
02010100.xhp
par_id3147035
help.text
IS NULL
02010100.xhp
par_id3159385
help.text
IS NULL returns all records for which the Yes/No field has neither of the states Yes or No (selected in gray).
02010100.xhp
par_id3157888
help.text
The syntax depends on the database system used. You should also note that Yes/No fields can be defined differently (only 2 states instead of 3).
02010100.xhp
hd_id3145772
help.text
Parameter queries
02010100.xhp
par_id191120151905346795
help.text
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.
02010100.xhp
par_id191120151905439551
help.text
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.
02010100.xhp
par_id191120151905518123
help.text
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 <link href="text/sdatabase/02010100.xhp#sqlmode">SQL mode</link> this should be typed as <item type="input">WHERE "Field" = :Parameter_name</item>
02010100.xhp
par_id191120151905584287
help.text
Parameter names may not contain any of the characters <item type="input"><space>`!"$%^*()+={}[]@'~#<>?/,</item>. They may not be the same as field names or SQL reserved words. They may be the same as aliases.
02010100.xhp
par_id191120151931441881
help.text
A useful construction for selecting records based on parts of a text field's content is to add a hidden column with <item type="input">"LIKE '%' || :Part_of_field || '%'"</item> as the criterion. This will select records with an exact match. If a case-insensitive test is wanted, one solution is to use <item type="input">LOWER (Field_Name)</item> as the field and <item type="input">LIKE LOWER ( '%' || :Part_of_field || '%' )</item> 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 <link href="text/sdatabase/02010100.xhp#sqlmode">SQL mode</link> this should be typed as <item type="input">LOWER ( "Field_Name" ) LIKE LOWER ( '%' || :Part_of_field || '%' )</item>.
02010100.xhp
par_id3150585
help.text
Parameter queries may be used as the data source for <link href="text/shared/02/01170203.xhp">subforms</link>, to allow the user to restrict the displayed records.
02010100.xhp
hd_id3151035
help.text
Parameter Input
02010100.xhp
par_id3153596
help.text
<ahelp hid="HID_QRYDGN_ROW_FUNCTION">The <emph>Parameter Input</emph> dialog asks the user to enter the parameter values. Enter a value for each query parameter and confirm by clicking <emph>OK</emph> or typing <emph>Enter</emph>.</ahelp>
02010100.xhp
par_id191120151924165870
help.text
The values entered by the user may consist of any characters which are allowable for the SQL for the relevant criterion; this may depend on the underlying database system.
02010100.xhp
par_id191120151939594217
help.text
The user can use the SQL wild-card characters "%" (arbitrary string) or "_" (arbitrary single character) as part of the value to retrieve records with more complex criteria.
02010100.xhp
hd_id3145181
help.text
SQL Mode
02010100.xhp
par_id3147013
help.text
SQL stands for "Structured Query Language" and describes instructions for updating and administering relational databases.
02010100.xhp
par_id3152570
help.text
In $[officename] you do not need any knowledge of SQL for most queries, since you do not have to enter the SQL code. If you create a query in the query designer, $[officename] automatically converts your instructions into the corresponding SQL syntax. If, with the help of the <emph>Switch Design View On/Off </emph>button, you change to the SQL view, you can see the SQL commands for a query that has already been created.
02010100.xhp
par_id3152412
help.text
You can formulate your query directly in SQL code. Note, however, that the special syntax is dependent upon the database system that you use.
02010100.xhp
par_id3146842
help.text
If you enter the SQL code manually, you can create SQL-specific queries that are not supported by the graphical interface in the <emph>Query designer</emph>. These queries must be executed in native SQL mode.
02010100.xhp
par_id3149632
help.text
By clicking the <link href="text/shared/02/14030000.xhp"><emph>Run SQL command directly</emph></link> icon in the SQL view, you can formulate a query that is not processed by $[officename] and sent directly to the database engine.
02010101.xhp
tit
help.text
Join Properties
02010101.xhp
bm_id3154015
help.text
<bookmark_value>links;relational databases (Base)</bookmark_value> <bookmark_value>inner joins (Base)</bookmark_value> <bookmark_value>joins in databases (Base)</bookmark_value> <bookmark_value>left joins (Base)</bookmark_value> <bookmark_value>right joins (Base)</bookmark_value> <bookmark_value>full joins (Base)</bookmark_value>

Loading…

User avatar None

String updated in the repository

LibreOffice Help - master / text/sdatabaseDzongkha

 
6 months ago
Browse all component changes

Glossary

English Dzongkha
No related strings found in the glossary.

String information

Context
02010100.xhp
par_id191120151905518123
help.text
Source string description
f2NMg
Source string location
02010100.xhp
String age
6 months ago
Source string age
6 months ago
Translation file
dz/helpcontent2/source/text/sdatabase.po, string 270