The translation is temporarily closed for contributions due to maintenance, please come back later.

Translation

02010101.xhp par_id3151205 help.text
English MzpBt
Context English Dzongkha Actions
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" name="subforms">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" name="Run SQL command directly"><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>
02010101.xhp
hd_id3154015
help.text
Join Properties
02010101.xhp
par_id3151205
help.text
If you double-click a connection between two linked fields in the query design, or if you choose <emph>Insert - New Relation</emph>, the <emph>Join Properties</emph> dialog appears. These properties will be used in all queries created in the future.
02010101.xhp
hd_id3155066
help.text
Tables involved
02010101.xhp
par_id3153924
help.text
<ahelp hid="dbaccess/ui/joindialog/table2">Specifies two different tables that you want to join.</ahelp>
02010101.xhp
hd_id3155766
help.text
Fields involved
02010101.xhp
par_id3148994
help.text
<ahelp hid=".">Specifies two data fields that will be joined by a relation.</ahelp>
02010101.xhp
hd_id3159267
help.text
Options
02010101.xhp
hd_id3147340
help.text
Type
02010101.xhp
par_id3152482
help.text
<ahelp hid="dbaccess/ui/joindialog/type">Specifies the join type of the selected join.</ahelp> Some databases support only a subset of the various possible types.
02010101.xhp
hd_id3155334
help.text
Inner Join
02010101.xhp
par_id3155936
help.text
<ahelp hid="dbaccess/ui/joindialog/type">In an inner join, the results table contains only those records for which the content of the linked fields is the same.</ahelp> In $[officename] SQL this type of link is created by a corresponding WHERE clause.
02010101.xhp
hd_id3156372
help.text
Left Join
02010101.xhp
par_id3166450
help.text
<ahelp hid="dbaccess/ui/joindialog/type">In a left join, the results table contains all records of the queried fields from the left table and only those records of the queried fields from the right table for which the content of the linked fields is the same.</ahelp> In $[officename] SQL this type of link corresponds to the LEFT OUTER JOIN command.
02010101.xhp
hd_id3155607
help.text
Right Join
02010101.xhp
par_id3150647
help.text
<ahelp hid="dbaccess/ui/joindialog/type">In a right join, the results table contains all records of the queried fields from the right table and only those records of the queried fields from the left table for which the content of the linked fields is the same.</ahelp> In $[officename] SQL this type of link corresponds to the RIGHT OUTER JOIN command.
02010101.xhp
hd_id3158215
help.text
Full Join
02010101.xhp
par_id3163665
help.text
<ahelp hid="dbaccess/ui/joindialog/type">In a full join, the results table contains all records of the queried fields from the left and right tables.</ahelp> In the SQL of $[officename] this type of link corresponds to the FULL OUTER JOIN command.

Loading…

No matching activity found.
Browse all component changes

Glossary

English Dzongkha
No related strings found in the glossary.

String information

Context
02010101.xhp
par_id3151205
help.text
Source string description
MzpBt
Source string location
02010101.xhp
String age
2 years ago
Source string age
2 years ago
Translation file
dz/helpcontent2/source/text/sdatabase.po, string 287