DJ> This is probably the only possible implementation unless there are fb
DJ> features I don't know about.

DJ> Are you proposing an additional ResultSet wrapper implementation with this
DJ> feature or modifying the existing one?  I'd be more comfortable with a
DJ> wrapper at this point, but will listen to arguments.  I'd like to keep the
DJ> most basic result set implementation as small and fast as possible.  Maybe
DJ> its an unreasonable bias, but I don't really see the need for the fancy
DJ> result sets/row set requirements.  I think using an app server is a better
DJ> idea.

I think a wrapper (let's say FBUpdatableResultSet) would be solution.
When an updatable result set is asked from the driver it would simply
instantiate FBUpdatableResultSet instead of FBResultSet.

Best wishes,
Daniel