The first part of this series discussed why you might use Theon as a Schema Management Tool for your PostgreSQL database. The second part part covered the necessary packages and installation. This final part is an introductory tutorial.
In the first part of this tutorial we created a database and started to manage it in Theon. In the second part we configured TheonCoupler to load data automatically into the database. In this third part we will configure TheonUI to allow access to the database and make a custom desktop. In the fourth and final part we will package and distribute the result.
Clear out existing derived content and generate the TheonUI metadata content and configuration file.
rm -fr derived ttkm derive ui
Start up a server instance using the just generated configuration file and content.
ttkm server ui using config=derived/ui/default/ui.conf
On a browser running on the local machine go to localhost:8000/ui.html to access our instance of TheonUI. Once there we can access the data in the package or rpmdata tables as follows.
From the Choose Desktop menu select Browser. From the Choose Cluster menu select All Clusters. From the Choose Table menu select package. Then the content will be accessible. Choose Use Grid option to see the content in a tabular form.
We can construct a desktop to show content from multiple related tables simultaneously. However at the moment our database is too simplistic for this. So first we will add another table which is a child of package and create a stream to load it with data. All aspects of this have been covered in part one and part two of this tutorial so much of the detail will be glossed over here.
Create a new table related to package and a corresponding data source table, import the new structure into Theon, then undo our changes and upgrade from Theon.
psql packages <<EOF CREATE TABLE packdep ( name TEXT, arch TEXT, requires TEXT, version TEXT ); CREATE TABLE rpmdeps AS SELECT * FROM packdep; ALTER TABLE package ADD PRIMARY KEY (name,architecture); ALTER TABLE packdep ADD FOREIGN KEY (name,arch) REFERENCES package (name,architecture); EOF ttkm import psql packages <<EOF DROP TABLE packdep; DROP TABLE rpmdeps; ALTER TABLE package DROP CONSTRAINT package_pkey; EOF ttkm export ttkm upgrade
Now modify the existing rpm Stream to add a new Couple with a custom source table and feed of data. Start the TheonUI first.
ttkm self server ui
Now enter the necessary data using a locally running browser pointed at localhost:8000/ui.html.
Open the Streaming desktop. On the first panel (Choose Model) ensure the right model is shown (in this case packages should be the only one) and then open the Stream panel and add one new row into the Couples box: Position SourceEntity TargetEntity Name[Info] 2 rpmdeps packdep rpmpackagedeps Open the Couple panel, make sure the rpmpackagedeps couple is shown and enter and save the following for the couple (keep quotes): Source Origin Value = 'RPM' Reload = Pipe Then add two new rows in the Bonds box: Position Type 1 Handle 2 Column Open the Bond panel and add rows in the Pairs box for each bond type as below: For Handle: Position SourceColumn TargetColumn 1 name name 2 arch arch 3 requires requires For Column: Position SourceColumn TargetColumn 1 version version
For the couple we have defined the source table (rpmdeps) and target table (packdep). We have also defined the handle pair (name:name + architecture:architecture + requires:requires) to tie records together between source and target.
Now exit the server process with Control-C.
Export the modified schema and upgrade the live database structures.
ttkm export ttkm upgrade
Update the stream configuration.
ttkm derive coupler
Run the stream, load the data and process the new couple to load the target table content. Then check that content.
rpm -qa --qf '["%{NAME}","%{ARCH}","%{REQUIRENAME}","%{REQUIREVERSION}"\n]'| ttkm stream agent rpm refresh to packdep couple packdep
psql packages -c "SELECT arch, COUNT(*) AS total FROM packdep GROUP BY arch;"
arch | total
--------+--------
(none) | 1
i486 | 99
noarch | 17006
i686 | 2631
x86_64 | 63068
(5 rows)
Now we have some related tables and data we can construct a desktop in TheonUI that in one panel allows package selection and shows the related package dependencies. Start up TheonUI for the Theon management database.
ttkm self server ui
Now enter the necessary data using a locally running browser pointed at localhost:8000/ui.html.
Open the Reflection desktop. On the first panel (Choose Model) ensure the right model is shown (in this case packages should be the only one). Add a new row in the Desktops box: Desktop-Label = packages Name[Info] = Packages Open the Panel panel and add one new row: Panel-Label = package Name[Info] = Package ? Base Entity = package Selector = Scroll and save the changes. Then add one new row in the Connectors box: Position ?JoiningRelationship Type Label 1 packdep_name_fkey ForwardNormal Requirements and save the changes. Then add one new row in the Presenters box: Presenter-Label Style Height Requirements Grid 16 and save the changes. Then add the following rows in the Fields box: Position ?Connector ?Attribute Presenter Width Name[Info] 1 -NONE- name - 80 Name 1 -NONE- architecture - 20 Architecture 1 -NONE- version - 20 Version 1 -NONE- release - 20 Release 5 Requirements requires Requirements 80 Name 6 Requirements version Requirements 20 Version and save the changes. Open the Desktop panel and add one new row into the Panels box: Position ?Panel Link-Label 1 package Package
Now exit the server process with Control-C.
Export the modified schema and derive the new UI metadata.
ttkm export rm -fr derived ttkm derive ui
Before starting the server tweak the configuration manually so that the initial data fetch size is limited. Then start up a server instance using the just generated configuration file and content.
Add at the top of the "config = {" section in derived/ui/default/ui.conf:
"limit_rows" : 250,
"limit_rows_conditionally" : True,
ttkm server ui using config=derived/ui/default/ui.conf
On a browser running on the local machine go to localhost:8000/ui.html to access our instance of TheonUI.
From the Choose Desktop menu select Packages.
This is a very simple demonstration desktop. You can use it to lookup a package by name at the top for example and each pre-requisite package and version will be shown in the lower box. Or you can query for a pre-requisite package name and all the packages dependent on it will be shown.
