I've got a very short 2 field form, but I have many instances of it, one for each of many dates. In most instances, a user will only update a single date or two, so loading the entire set of values, and then looking them back up in the primary key convertor is needlessly wasteful, so I'd rather have a different form on each row, where one column can just be a submit button.
This is easy enough to do when just iterating with a For component, but strikes me as enormously more difficult in contrib:Table, mostly because the TapestryTables.war examples don't address the problem at all, and there doesn't seem to be any alternative documentation of contrib:Table. Since I'd like the sorting and paging functionality of contrib:table, I am hoping that someone else has done this. The structure is basically a date column which just displays a date, then 2 text input boxes in 2 more columns, then a submit button in a 4th column. The primary key is also the date. It seems like, if I use the single form per table example from TapestryTables.war, I would have to load the values for the entire dataset, update the 1 or 2 changed rows, and then save them back to the database, which isn't terribly efficient. Guidance, anyone? Thanks Tap4, tomcat 5.5, linux, mysql --sam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
