Re^4: Pivoting parts of a database table into an HTML table

Thank you, that helped a lot. I guess my problem was trying to force two state change points (date and type), which makes quite a bit sense but apparently introduces too much complexity I can't deal with.

Comment on Re^4: Pivoting parts of a database table into an HTML table

Replies are listed 'Best First'.
Re^5: Pivoting parts of a database table into an HTML table by jandrew (Chaplain) on Oct 24, 2012 at 17:37 UTC
You could use type as a state change point but your column allocation would fail for 03 Oct (Wed) since the first type was not available that day. If you reversed the type sort order then you would fail on 29 Sep (Sat) and 02 Oct (Tue) for the same reason. To allocate the correct content to the correct column then you need to pre-define type names applied to the column and still store both sets of type content until the date changed. Doing that you loose any (minor) memory advantage gained from recursively parsing the type. You would also have problems if three types were defined later and you only wanted to display two.	[reply]

Replies are listed 'Best First'.

Re^5: Pivoting parts of a database table into an HTML table
by jandrew (Chaplain) on Oct 24, 2012 at 17:37 UTC

You could use type as a state change point but your column allocation would fail for 03 Oct (Wed) since the first type was not available that day. If you reversed the type sort order then you would fail on 29 Sep (Sat) and 02 Oct (Tue) for the same reason. To allocate the correct content to the correct column then you need to pre-define type names applied to the column and still store both sets of type content until the date changed. Doing that you loose any (minor) memory advantage gained from recursively parsing the type. You would also have problems if three types were defined later and you only wanted to display two.

[reply]