Re: SQL for presentation

From: Kenneth Downs <knode.wants.this_at_see.sigblock>
Date: Thu, 06 Jul 2006 07:05:05 -0400
Message-Id: <lc7vn3-tla.ln1@pluto.downsfam.net>

frebe73_at_gmail.com wrote:

>> >> Jumping from a SELECT to HTML is difficult to picture here.
>> >
>> > I think so too, but lets say we had a better relational language and a
>> > relational schema for a html document, instead of a hierachial xml
>> > document?
>> >
>>
>> It's hard for me to picture, can you provide more detail on what you
>> think it may look like?

>
> Does "it" refer to relational language or the relational schema? In
> case schema, I have something like this in mind.
>
> html(docid, title, bodyelementid)
> element(elementid, seqno, parentid)
> form(elementid, action)
> input(elementid, type, name, value)
> table(elementid, border)
> tr(elementid, rowno)
> etc etc
>
> /Fredrik

I guess what I meant was a specific example of a body of data, one or more rows from one or more tables, converted into a body of HTML. If you gave an example of a starting point and an ending point, I might begin to get a feel for how you would picture jumping from one to the next. The data should be customer data, like orders, not data from a HTML schema like the one above.

Personally I'm a fanatic for automation, and I automated normal table maintenance screens down to zero coding, but custom screens are for me the only thing left that is manually coded case-by-case. If you are working out a way to hit those cases, I'm all ears.

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

Received on Thu Jul 06 2006 - 06:05:05 CDT