>> >* It would be great to be able to bound the growth of the in-memory db
What would happen when you reached that bound? Would it be similar to
running out of disk space for a disk-resident DB (i.e., your transaction
is aborted, and you get an exception)?
If so, then what do you do? Would the application then increase the bound,
and expect to resume adding data to their in-memory DB?
Or would the application then drop tables, delete rows from tables, etc.,
and then expect to resume adding data to their in-memory DB?
thanks,
bryan