Skip to main content

Creating a network planning using hierarchical queries

Assume we have a table of locations like
Name                                      Null?    Type
----------------------------------------- -------- -----------------
ID NOT NULL NUMBER
NAME NOT NULL VARCHAR2(50)
and a table of possible lines (or route parts) like
Name                                      Null?    Type
----------------------------------------- -------- --------
ID NOT NULL NUMBER
FROM_LOC_ID NOT NULL NUMBER
TO_LOC_ID NOT NULL NUMBER
DISTANCE NOT NULL NUMBER
How can we calculate the best route (in this case: the route with the shortest distance) from a startpoint to an endpoint?
The answer is: By using an hierarchical query:
select dep_name
, arr_name
, route
, distance
, execute(distance) total
from
(
select connect_by_root dep.id dep_id
, connect_by_root dep.name dep_name
, arr.id arr_id
, arr.name arr_name
, level stops
, substr(sys_connect_by_path(dep.name||'-'||arr.name, '->'),3) route
, substr(sys_connect_by_path(lne.id, ','),2) lne_ids
, substr(sys_connect_by_path(lne.distance, '+'),2) distance
from lines lne
, locations dep
, locations arr
where lne.from_loc_id = dep.id
and lne.to_loc_id = arr.id
connect by nocycle prior arr.id = dep.id
)
where dep_name = 'MAASTRICHT'
and arr_name='AMSTERDAM'
ORDER BY 5 ASC
(Remark: The function 'execute' does nothing but returning the result of an execute immediate of a string value).
The outcome of this query is a list of all defined routes from Maastricht to Amsterdam with the shortest route shown first. The
"substr(sys_connect_by_path(dep.name||'-'||arr.name, '->'),3) route"
column returns the route like
"MAASTRICHT-EINDHOVEN->EINDHOVEN-UTRECHT->UTRECHT-AMSTERDAM"
The column
"substr(sys_connect_by_path(lne.distance, '+'),2)"
returns a string that represents the distances to sum:
"86,7+93,6+44,7"
This column is used for calculating the total distance.

So you can use hierarchical queries for a lot more purposes than the obvious who-is-the-manager query.
Ofcourse you won't use this kind of solution to calculate distances (there are far better webservices available for that). In 'real life' we've used this approach (but more elaborated and a lot more difficult) to get the cheapest supplier for the movement of goods from a to b.

Comments

Popular posts from this blog

Filtering in the APEX Interactive Grid

Remember Oracle Forms? One of the nice features of Forms was the use of GLOBAL items. More or less comparable to Application Items in APEX. These GLOBALS where often used to pre-query data. For example you queried Employee 200 in Form A, then opened Form B and on opening that Form the Employee field is filled with that (GLOBAL) value of 200 and the query was executed. So without additional keys strokes or entering data, when switching to another Form a user would immediately see the data in the same context. And they loved that. In APEX you can create a similar experience using Application Items (or an Item on the Global Page) for Classic Reports (by setting a Default Value to a Search Item) and Interactive Reports (using the  APEX_IR.ADD_FILTER  procedure). But what about the Interactive Grid? There is no APEX_IG package ... so the first thing we have to figure out is how can we set a filter programmatically? Start with creating an Interactive Grid based upon the good old Employ

apex_application.g_f0x array processing in Oracle 12

If you created your own "updatable reports" or your custom version of tabular forms in Oracle Application Express, you'll end up with a query that looks similar to this one: then you disable the " Escape special characters " property and the result is an updatable multirecord form. That was easy, right? But now we need to process the changes in the Ename column when the form is submitted, but only if the checkbox is checked. All the columns are submitted as separated arrays, named apex_application.g_f0x - where the "x" is the value of the "p_idx" parameter you specified in the apex_item calls. So we have apex_application.g_f01, g_f02 and g_f03. But then you discover APEX has the oddity that the "checkbox" array only contains values for the checked rows. Thus if you just check "Jones", the length of g_f02 is 1 and it contains only the empno of Jones - while the other two arrays will contain all (14) rows. So for

Stop using validations for checking constraints !

 If you run your APEX application - like a Form based on the EMP table - and test if you can change the value of Department to something else then the standard values of 10, 20, 30 or 40, you'll get a nice error message like this: But it isn't really nice, is it? So what do a lot of developers do? They create a validation (just) in order to show a nicer, better worded, error message like "This is not a valid department".  And what you then just did is writing code twice : Once in the database as a (foreign key) check constraint and once as a sql statement in your validation. And we all know : writing code twice is usually not a good idea - and executing the same query twice is not enhancing your performance! So how can we transform that ugly error message into something nice? By combining two APEX features: the Error Handling Function and the Text Messages! Start with copying the example of an Error Handling Function from the APEX documentation. Create this function