Rules for Valentina DB maintenance

[Trevor DeVore]

On Jan 29, 2004, at 1:40 AM, Ruslan Zasukhin wrote:

> on 1/29/04 2:17 AM, Trevor DeVore at lists at mangomultimedia.com wrote:
>
> Hi Trevor,
>
>> I will be releasing my first Revolution software title which uses
>> Valentina for the database in the near future.  I'm wondering if I 
>> need
>> to build in a periodic call which will call the compact, defragment,
>> etc. calls after it has been installed on the customers system.
>
> May be better give this as menu functions for user?
> Also good to have XML dump/load

Good idea.  In my case I will probably make some sort of key 
combination to run these if the need arises.  The database isn't used 
for entering any sort of data, it just holds data that we've entered 
which the Revolution app uses to build it's interface, display 
information, etc.  There is some information stored on QTVRs (last pan, 
tilt, etc.) which gets updated while using the program but that is it.

>> Most of the tables will only have a read performed on them.  There are
>> one or two tables that have data updated in them on occasion.  Are
>> there any rules for how often compact, defragment, etc.?
>
> COMPACT you need only after MANY DELETEs
>
> DEFRAGMENT -- after MANY INSERTS.

So if I am just updating values already entered in the database I 
shouldn't have to run any of these it seems.

Thanks,

-- 
Trevor DeVore
Blue Mango Multimedia
trevor at mangomultimedia.com