Mercurial > hg > ltpda

comparison m-toolbox/html_help/help/ug/repo_gui_query_content.html @ 0:f0afece42f48

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Import.
author Daniele Nicolodi <nicolodi@science.unitn.it>
date Wed, 23 Nov 2011 19:22:13 +0100
parents
children
comparison
equal deleted inserted replaced
-1:000000000000 0:f0afece42f48
1 <p>
2 Querying an LTPDA repository is done using standard SQL statements. The repository GUI
3 presents the user with the possibility to graphically build SQL statements which avoids
4 learning SQL syntax. Currently, the SQL statements that can be built in this way are
5 restricted to queries on a single database table. High-level queries, searching more database tables at once, are implemented in the following panel.
6 </p>
7 <p>
8 The repository GUI has a query panel which looks like the figure below:
9 </p>
10 <br>
11 <br>
12 <img src="images/repo_gui_query_1.png" alt="Repo GUI Query">
13 <br>
14 <br>
15 <p>
16 In this figure, you see that the user has built a query to select all objects
17 submitted on the 24th February 2008. The results will contain the object id,
18 the submitted date, the experiment title, the experiment description, and the analysis
19 description. The results will be sorted in descending order of the object id.
20 </p>
21 <p>
22 Executing the query (click the 'Execute query' button) produces the results table
23 shown below.
24 </p>
25 <br>
26 <br>
27 <img src="images/repo_gui_query_2.png" alt="Repo GUI Query Results">
28 <br>
29 <br>
30 <p>
31 The query string that is actually executed is presented in the text edit
32 box above the 'Execute query' button. This query string can be edited to allow for finer
33 control over the query. This is meant for users who already have a working knowledge of MySQL
34 SQL syntax.
35 </p>
36