Title: CForms(woody) ad hibernate design advice needed

I need to develop a large number of database maintenance pages with create/read/update/delete functionality (e.g. users, items, regions, etc.).  Repeater widgets and actions provide an easy way to display multiple rows and edit them in place.  However, it seems like the only simple way to update a database is to delete every row and then re-insert the contents of the repeater.  This unfortunately doesn't scale with large results sets.  Is there a better way?  Thanks in advance.

Fyi, I'm planning to use hibernate from flow for serialization (thanks Hugo for the samples!).

joel

Joel McConaughy
Managing Partner
Displayware
800 Fifth Ave., #101-316
Seattle, WA 98104-3191
206-300-4732 Direct
206-382-2188 Fax
[EMAIL PROTECTED]

Reply via email to