Re: SQL for presentation

frebe73_at_gmail.com wrote:

>
> The starting data could be an employee table.
> employee(employeeid, firstname, lastname)
> With the content
> employee(1, "Donald", "Duck")
> employee(2, "Kit", "Walker")
>
> The end-point might be tuples describing the html page.
>
> html(1, "Employee list", 100)
> element(100, 1, null)
> element(101, 1, 100)
> table(101, 1)
> element(102, 1, 101)
> tr(102)
> element(104, 1, 102)
> td(104, "Donald")
> element(105, 1, 102)
> td(105, "Duck")
> element(103, 1, 101)
> tr(103)
> element(104, 1, 102)
> td(104, "Kit")
> element(105, 1, 102)
> td(105, "Walker")
>
> The result tuples would if possible be obtained by a view (or something
> similar using any declarative relational language).

In practical terms I'm not sure what the benefit of this is. If we can get from the two employee rows to the HTML itself, why introduce an intermediate step?

-- 
Kenneth Downs
Secure Data Software, Inc.
(Ken)nneth@(Sec)ure(Dat)a(.com)