Module
Contents
Index 🔎︎

# Xa'mote Akata

Xa'mote Akati Illachi daatubeeze xa'mo kalaqattora nna muccisattora fajjannohe.

Tene hajajo injeesate...

In a database file window, click the Queries icon, then choose Edit - Edit.

Roore daatubeezubba meemiisate woy daatubeeze dirate komipiyuterekki aana maareekkubba leellishate xa'mubba horoonsiranno. Illachubba xa'mubbate gede mittu dani assiishsha uyitanno, ikkollana owaataanchu midaadi aana. Daatubeeze illachubba irkisanno owaataanchi aana ikkituro, leellishate yanna ranke ledate owaataanchu aana maareekkubba meemiisate illachubba horoonsira dandaatto.

Tenne Illacha kalaqi hajao Shaubbate daatubeeze bortaje gaxi qooliwiinni dooratenni, Illachu Akati xullaallo Xa'mote Akata xullaallo kowiicho xawisa dandaatto.

Xa'mote Akati xullaallo ofolla kalaqantino xa'mora kuusantino, ikkollana kalaqamino illachi giddo kuusama didandiitanno.

## Akatu Illacha

Xa'mo kalaqate, daatubeeze bortaje giddo xa'mubbate bido qiphisi , aanchite Akatu Illachi giddo xa'mo Kalaqiqiphisi.

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.

Xa'mote Akati Illachi xullaallo sammo giddo, bidubba Xa'mote Akati Gaxi nna Akatu gaxubba leellitanno.

Xa'mo jifa hasirittoro, daatubeeze bortaje giddo xa'mote su'ma lameegge qiphisi. Shaete giddo leellino xa'mote gumidaatu bue illachi ledo mittu danho. Qaagi: shaete leella yannate geeshshira callaati.

### Xa'mote Akati Illachi giddo Qulfubba

Qulfe | Assiishsha
F4 | Balaxilacha
F5 | Harate Xa'mo
F7 | Shae woy Xa'mo Ledi

## Soroowi

When you open the query design for the first time, you see a dialog in which you must first select the table or query that will be the basis for your new query.

Barubba xa'mote ledate lameegge qiphisi. Fixoomubbate tirate goshooshi-nna-wori.

Xa'mo akatamanta geeshsha, doorantino shaubba soorra didandaatto.

### Shaubba hooli

Shaubba Akatu illachiwiinni hoolate, cshaete xullaallo aliidi qacce qiphisi nna eigaru mayino leellishi. Shae Akatu Illachiwiinni hoolate Huni hajajo horoonsira dandaatto. Wole doorshi Hunate Qulfe xiiwateeti.

### Shae harisi nna shaete bikka soorri

Shaubba doorshikki garinni marbikka nna qineessa dandaatto. Shaubba harisate, aliidi qacce hasirootto dargira goshooshi. Leellitino shaete ofolla ajote wirrisinni hasirootto bikka iillate shaete qacce woy meereero goshooshi.

## Shaete Fiixoomubba

Daatu fiixoomubba mitte shae barete su'minna wole sha barete su'mi giddo heedhuro, xa'mokkira hakkuri fiixoomubba horoonsira dandaatto.

If, for example, you have a spreadsheet for articles identified by an article number, and a spreadsheet for customers in which you record all articles that a customer orders using the corresponding article numbers, then there is a relationship between the two "article number" data fields. If you now want to create a query that returns all articles that a customer has ordered, you must retrieve data from two spreadsheets. To do this, you must inform LibreOffice about the relationship which exists between the data in the two spreadsheets.

To do this, click a field name in a table (for example, the field name "Item-Number" from the Customer table), hold down the mouse button and then drag the field name to the field name of the other table ("Item-Number" from the Item table). When you release the mouse button, a line connecting the two fields between the two table windows appears. The corresponding condition that the content of the two field names must be identical is entered in the resulting SQL query.

Batinyu fiixoomme shittuwa kaiminni xa'mo kalaqa dandiinannihu LibreOffice reqecciimo fixoomitete daatubeeze gede horoonsirittoro callaati.

Shaubba xa'mote giddo babbaxxitino daatubeezubbawiinni injeessa didandaatto. Xa'mubba batinye shaubba abbitannohu mitte daatubeeze giddo calla kalaqanturooti.

### Specifying the relation type

If you double-click on the line connecting two linked fields or call the menu command Insert - New Relation, you can specify the type of relation in the Relations dialog.

Doorshunni, xuruuru doorama geeshsha giggishsha xiiwi, aanchite eigaru mayino leellishate shiikki+F10 xiiwi nna hakko Muccisidoori. Gamu daatubeezubba dandaamano xaadisi danubbara cinaancho calla irkissanno.

### Fiixoomubba huna

Lame shaubba mereero fiixoomubba hunate amadisiishshu xuruura qiphisi nna aanchite huni qulfe xiiwi.

Doorshunni, Barubba noo giddo Fiixoomubbate hasaawi giddo hasiissanno eubba huni. Woy shiimunni xaadino worbichi leella geeshsha giggishsha xiiwi, antete eigaru mayino fanate Shift+F10 xiiwi nna Huni hajajo doori.

## Defining the query

Xa'mo tirate ikkitubba doori. Akatu shaehu mittu mittunku caccafoxa'mote daatu bare adhitanno. Ikkitubba mitte haawiittimma giddo Boolean AND nni xaaddino.

### Specifying field names

First, select all field names from the tables that you want to add to the query. You can do this either by drag-and-drop or by double-clicking a field name in the table window. With the drag-and-drop method, use the mouse to drag a field name from the table window into the lower area of the query design window. As you do this, you can decide which column in the query design window will receive the selected field. A field name can also be selected by double-clicking. It will then be added to the next free column in the query design window.

### Barete su'muwa huna

Xa'motewiinni barete su'ma hoolate, barete caccafote umaallo qiphisi nna caccafote eigari aana Huni hasaawa doori.

### Saving the query

Use the Save icon on the Standard toolbar to save the query. You will see a dialog that asks you to enter a name for the query. If the database supports schemas, you can also enter a schema name.

#### Loosichimma

Xa'mote woy shaete illachira gaamaminoha loosichimmate su'ma ei.

#### Xa'mote su'ma woy shaete illachi su'ma

Xa'mote su'ma woy shaete illachi su'ma.

### Daata meemiissa

To filter data for the query, set the desired criteria in the lower area of the query design window. The following options are available:

#### Bare

Enter the name of the data field that is referred to in the Query. All settings made in the filter option rows refer to this field. If you activate a cell here with a mouse click you'll see an arrow button, which enables you to select a field. The "Table name.*" option selects all data fields with the effect that the specified criteria will be applied to all table fields.

#### Soorrote su'ma

Specifies an alias. This alias will be listed in the query instead of the field name. This makes it possible to use user-defined column labels. For example, if the data field is named PtNo and, instead of that name, you would like to have PartNum appear in the query, enter PartNum as the alias.

In a SQL statement, aliases are defined as follows:

Caccafoota shaete FROM soorrote su'mi AS SELECT.

Lawishshaho:

SELECT "PtNo" AS "PartNum" FROM "bisubba"

#### Shae

The corresponding database table of the selected data field is listed here. If you activate this cell with a mouse click, an arrow will appear which enables you to select a different table for the current query.

#### Diri

If you click on this cell, you can choose a sort option: ascending, descending and unsorted. Text fields will be sorted alphabetically and numerical fields numerically. For most databases, administrators can set the sorting options at the database level.

#### Leellado

If you mark the Visible property for a data field, that field will be visibly displayed in the resulting query. If you are only using a data field to formulate a condition or make a calculation, you do not necessarily need to display it.

#### Wonshiworcho

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

#### woy

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

You can also use the context menu of the line headers in the lower area of the query design window to insert a filter based on a function:

### Assiishshubba

The functions which are available here depend on those provided by the database engine.

If you are working with the embedded HSQL database, the list box in the Function row offers you the following options:

Dooro | SQL | Heleelle
Assiishshu dino |  | Loosamanno assiishshi dino.
Mereerima | AVG | Barete aritimeetike mereerima shallaganno.
Kiiro | COUNT | Determines the number of records in the table. Empty fields can either be counted (a) or excluded (b). a) COUNT(*): Beeddakkicho shaete giddo yekkeeramme baala mareekuwa kiirtanno gede sa'anno. b) COUNT(column): Passing a field name as an argument counts only those records for fields in which the field name in question contains a value. Records with fields having Null values (i.e. fields containing no characters) will not be counted.
Jawiidi | MAX | Determines the highest value of a record for that field.
Shiimiidi | MIN | Determines the lowest value of a record for that field.
Ledo | SUM | Calculates the sum of the values of records for the associated fields.
Gaamo | GROUP BY | Groups query data according to the selected field name. Functions are executed according to the specified groups. In SQL, this option corresponds to the GROUP BY clause. If a criterion is added, this entry appears in the SQL HAVING sub-clause.

Qolteno suwashshu garinni assiishshu woshshatto SQL hedote fooliishshora eessa dandaatto. Ganallote:

SELECT FUNCTION(caccafo) FROM shae.

Lawishshaho, assiishshu SQL giddo ledo shallagate woshshi:

SELECT SUM("waaga") FROM "Gufo".

Except for the Group function, the above functions are called Aggregate functions. These are functions that calculate data to create summaries from the results. Additional functions that are not listed in the list box might be also possible. These depend on the specific database engine in use and on the current functionality provided by the Base driver used to connect to that database engine.

To use other functions not listed in the list box, you must enter them manually under Field.

You can also assign aliases to function calls. If you do not want to display the query string in the column header, enter a desired substitute name under Alias.

SQL hedote fooliishsho giddo fiixoomino assiishshaati:

SELECT FUNCTION() AS su'ma soorri FROM shae

Lawishsha:

SELECT COUNT(*) AS kiiro FROM "Uduunnicho"

If you run such a function, you cannot insert any additional columns for the query other than as an argument in a "Group" function.

Lawishshubba

Aananno lawishshi giddo, xa'mo lame shaubba giddoonni hadhanno: "Uduunnichu" shae "Uduunnichu-Kiiro" bare nna "Shiqishaano" shae "Shiqishaanchu-su'mi" bare ledo. Ledotenni, lamunku shaubba gutu bare su'ma "Shiqishaanchu kiiro afidhino."

Aantanno qaafubba baala shiqishaano sasu uduunne aleelli shiqishshannore xa'muwa kalaqate shiqqinoreeti.

1. Konni "Uduunnu " nna "shiqishaanote" shaubba xa'mote akatira surki.

2. Balaxe konni ledo fiixoomu noosikkiro lame shaubbaha "Shiqishaanchu_Kiiro" xaadisi.

3. Double-click on the "Item_No" field from the "Item" table. Display the Function line using the context menu and select the Count function.

4. Konne >3 wonshiworchote gede ei nna leellado bare dandiiweelsi.

5. Double-click the field in the "Shiqishaanote" shae giddo "Shiqishaanchu_Sumi" lameegge-qiphisi nna gaamote assiishsha doori.

6. Xa'mo harisi.

Kuni "Waagi" (uduunnichoho umu umu waagi) nna "Shiqishaanchu_Kiiro" (uduunnichu shiqishaanchira) barubba "Uduunnichu" shae giddo heedhuro, shiqishaanchu aantanno xa'monni shiqishino uduunnichiha mereerima guma afira dandaatto:

1. Konni "Uduunnichu " shae xa'mote akatira surki.

2. "Waaga" nna "Shiqishaanchu_Kiiro" barubba lameegge-qiphisi.

3. Asiishshu xuruura dandeessi nna "waagu" barewiinni mereerima assiishsha doori.

4. Qolteno "Mereerima" xuruuru giddo soorrote su'mi su'mira (maqishshu malaati nookkiha)ea dandaatto.

5. "Shiqishaanchu_Kiiro" barera gaamo doori.

6. Xa'mo harisi.

Aantanno eigaru mayinu hajajaano nna malaatta qaraho:

### Assiishshubba

Shows or hides a row for the selection of functions.

### Shaete Su'ma

Shaete su'mira haawiittimma leellishanno woy maaxanno.

### Soorrote su'mi Su'ma

Soorrote su'mi Su'mira haawiittimma leellishanno woy maaxanno.

### Coite Hornuwa

Retrieves only distinct values from the query. This applies to multiple records that might contain several repeating occurrences of data in the selected fields. If the Distinct Values command is active, you should only see one record in the query (DISTINCT). Otherwise, you will see all records corresponding to the query criteria (ALL).

Lawishshaho, "Culku loosaanchi" su'mi teessokki daatubeeze giddo batinye hige leellanno, xa'mote giddo mitteege calla leellino "Culku loosaanchi" su'ma badate Coitte Hornyuwa hajajoto doora dandaatto.

Batinye barubba xa'mora, Baala barubawiinni xaaddino hornyuwa addita ikka noose ikkitinohura gumu baxxitino maareekkonni suudisama dandaanno. Lawishshaho, "Culku loosaanchi Chikaago" giddo noohero teessokki maxaafi giddo mitte hige nna "Culku loosaanchi Londonete" giddo lameege heerannohe. Coitte Hornyuwa hajajonni, xa'mo lame barubba horoonsidhanno "Ahaahu su'ma" nna "katama" xa'mote guma "Culku loosaanchi Chikaago" giddo mitteege nna "Culku loosaanchi Londonete" giddo lameege qolanno.

SQL giddo, tini hajajo DISTINCT aana uurre loosannohura fiixoontanno.

### Limit

Allows you to limit the maximum number of records returned by a query.

If a Limit construction is added, you will get at most as many rows as the number you specify. Otherwise, you will see all records corresponding to the query criteria.

### Meemiisate ikkitubba loosiisanno

When formulating filter conditions, various operators and commands are available to you. Apart from the relational operators, there are SQL-specific commands that query the content of database fields. If you use these commands in the LibreOffice syntax, LibreOffice automatically converts these into the corresponding SQL syntax via an internal parser. You can also enter the SQL command directly and bypass the internal parser. The following tables give an overview of the operators and commands:

Assaancho | Tiro | Ikkito ...ikkiro duushshitanno
= | taalanno | ... barete amado shallagote handaarira leellitinoti mittu danite. The operator = will not be displayed in the query fields. If you enter a value without any operator, the = operator is automatically assumed.
<> | ditaalanno | ... barete amado baxxitino shallagote handaarira difiixoontanno.
> | rooranno | ... barete amado baxxitino shallagote handaarinni roortanno.
< | ajanno | ... barete amado baxxitino shallagote handaarinni ajjanno.
>= | rooranno woy taalanno | ... barete amado baxxitino shallagote handaarinni roortanno woy taaltanno.
<= | ajanno woy taalanno | ... barete amado baxxitino shallagote handaarinni ajjanno woy taaltanno.

LibreOffice hajajo | SQL hajajo | Tiro | Ikkito ...ikkiro duushshitanno
IS EMPTY | IS NULL | onaho | ... the field contains no data. For Yes/No fields with three possible states, this command automatically queries the undetermined state (neither Yes nor No).
IS NOT EMPTY | IS NOT NULL | dimullichote | ... the field is not empty, i.e it contains data.
LIKE placeholder (*) for any number of characters placeholder (?) for exactly one character | LIKE placeholder (%) for any number of characters Placeholder (_) for exactly one character | miilaati | ... the data field must contain the indicated search string in the order given. The position of the (*) placeholder indicates whether the searched for string (x) occurs before the placeholder (x*), after the placeholder (*x) or between the placeholders (*x*). Instead of the familiar file system (*) placeholder, you can also use the SQL (%) character as a placeholder in SQL queries in the LibreOffice interface. The (*) or (%) placeholder stands for any number of characters. The question mark (?) in the LibreOffice interface or the underscore (_) in SQL queries is used to represent exactly one character.
NOT LIKE | NOT LIKE | Miila di"ikkino | ... the field does not contain data having the specified expression.
BETWEEN x AND y | BETWEEN x AND y | [x,y] fanfe giddo uwanno | ... the field contains a data value that lies between the two values x and y.
NOT BETWEEN x AND y | NOT BETWEEN x AND y | [x,y] fanfe giddo diuwanno | ... the field contains a data value that does not lie between the two values x and y.
IN (a; b; c...) Note that semicolons are used as separators in all value lists! | IN (a, b, c...) | a, b, c amadino... | ... the field name contains one of the specified expressions a, b, c,... Any number of expressions can be specified, and the result of the query is determined by a boolean OR operator. The expressions a, b, c... can be either numbers or characters
NOT IN (a; b; c...) | NOT IN (a, b, c...) | a, b, c diamadino... | ... the field does not contain one of the specified expressions a, b, c,...
= TRUE | = TRUE | Addu hornyo afirino | ... barete sumi hornyo Adda afirino.
= FALSE | = FALSE | Kaphu hornyo afirino | ... the field data value is set to false.

### Lawishshuwa

='Ms.' | kuni "Ms." barete amadonni barete su'muwa qolanno
<'2001-01-10' | returns dates that occurred before January 10, 2001
LIKE 'g?ve' | returns records with field content such as "give" and "gave".
LIKE 'S*' | returns records with field contents such as "Sun".
BETWEEN 10 AND 20 | returns records with field content between the values 10 and 20. (The fields can be either text fields or number fields).
IN (1; 3; 5; 7) | returns records with the values 1, 3, 5, 7. If the field name contains an item number, for example, you can create a query that returns the item having the specified number.
NOT IN ('Smith') | returns records that do not contain "Smith".

Lawooshshe Luxuphi Aante: {luxuphi 'luxuphi-fikiima'}

Lawishshaho: ItemName *%' {escape '*'}uduunnichiwiinni * doori

Aamamannohe lawishshi ' *' hanafanno baalu uduunnichi su'mi eubaati. Togo yaano fikiimoota hasate dandaatto ikka hoogiro dargu amadaano garinni tirama noosi insano *, ?, _, % or uurrinshu malaatinni.

Gobayiidi Xaado Aante Amada: {oj outer-join}

Lawishsha: gufo Doori.* wiinni{oj udunnicho LEFT OUTER JOIN aantubba ON uduunnicho.no=aantubba.ANR}

### Borrote barubba xa'mamme

To query the content of a text field, you must put the expression between single quotes. The distinction between uppercase and lowercase letters depends on the database in use. LIKE, by definition, is case-sensitive (though some databases don't interpret this strictly).

### Barru barubba xa'mamme

Date fields are represented as #Date# to clearly identify them as dates. Date, time and date/time constants (literals) used in conditions can be of either the SQL Escape Syntax type, or default SQL2 syntax.

Date Type Element | SQL Escape syntax #1 - may be obsolete | SQL Escape syntax #2 | SQL2 syntax
Barra | {D'YYYY-MM-DD'} | {d 'YYYY-MM-DD'} | 'YYYY-MM-DD'
Yanna | {D'HH:MM:SS'} | {t 'HH:MI:SS[.SS]'} | 'HH:MI:SS[.SS]'
DateTime | {D'YYYY-MM-DD HH:MM:SS'} | {ts 'YYYY-MM-DD HH:MI:SS[.SS]'} | 'YYYY-MM-DD HH:MI:SS[.SS]'

Lawishsha: select kalqete.dirrawiinni select {d '1999-12-31'} doori

Example: select * from mytable where years='1999-12-31'

All date expressions (date literals) must be enclosed with single quotation marks. (Consult the reference for the particular database and connector you are using for more details.)

### Ee/dee'ni barubba xa'mamme

Ee/dee'ni barubba xa'mate, dBASE shaubbara aantanno ganallo horoonsiri:

Deerra | Xa,mote wonshiworcho | Lawishsha
Ee | dBASE shaubbara: ayeeti aamantino hornyo ditaaloho | =1 Ee/Dee'ni bare "Ee" woy "fani" (kolishunni dooraminoha)baala maareekuwa qolanno,
Dee''ni | . | =0 Ee/Dee'ni bare "Dino" woy "cufi" (doorshu dino)baala maareekuwa qolanno.
Ona | IS NULL | IS NULL Ee/Dee'ni bare (bullunni doorantinota)Ee woy dee'ni deerri baala mareekuwa qolanno.

Ganallo daatubeeze amuraati horo aana irkidhanno. Qolteno Ee/dee'ni barubba babbaxxitino garinni tirama dandaa noose (3 darga 2 deerri callu).

### Eishshu xa'mubba

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

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 || '%' ).

Parameter queries may be used as the data source for subforms, to allow the user to restrict the displayed records.

### Eishshu Eo

The Parameter Input dialog asks the user to enter the parameter values. Enter a value for each query parameter and confirm by clicking OK or typing Enter.

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.

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.

## SQL Gara

SQL " Ganammete Xa'mo Afoo"riqibbanno nna fixooma daatubeezubba yanneessora nna gashshora hajajubba xawisanno.

In LibreOffice 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, LibreOffice automatically converts your instructions into the corresponding SQL syntax. If, with the help of the Switch Design View On/Off button, you change to the SQL view, you can see the SQL commands for a query that has already been created.

You can formulate your query directly in SQL code. Note, however, that the special syntax is dependent upon the database system that you use.

If you enter the SQL code manually, you can create SQL-specific queries that are not supported by the graphical interface in the Query designer. These queries must be executed in native SQL mode.

By clicking the Run SQL command directly icon in the SQL view, you can formulate a query that is not processed by LibreOffice and sent directly to the database engine.