🚀 go-pugleaf

"Bill Todd" <no@no.com> skrev i meddelandet 
news:437b43c6$1@newsgroups.borland.com...
> Magnus Flysjv wrote:
>
>> I have the same problem.
>> But this is on a 6.0.2.0 version.
>>
>> We have an application that never commited as often as it should.
>> When the application is close and commit was called, we lost all data
>> and I have no idea why.
>
> Did you run gfix on the database to see if it has become corrupt?
>

Yes, gfix and gbak.. and it was only some page errors..
The GDB file was never corrupted so that it couldn't be opened in Interbase.

> Are you sure you committed all active transactions before the
> application was closed? If you close the program with a transaction
> active it will be rolled back, not committed.
>

The code below is from the Delphi sourcecode for the application, upon 
destruction of the class that handles all the database actions
...
 FStoredProc.Free;
 FSQL.Free;
 FQuery.Free;
 if FTransaction.Active then begin
  FTransAction.Commit;
  FTransAction.Active := false;
 end;
 FDatabase.Close;
 FTransaction.free;
 FDatabase.free;
...

>>
>> Also, the GDB file grown very fast.. but if I use gbak and gfix, the
>> file is shrinken from 32MB to only 2MB.
>
> Long running transactions disable garbage collection. This allows
> garbage record versions to accumulate in the database if you hare doing
> a lot of updates or deletes which, in turn, will cause the database
> file to grow.

There is at least one update per minute.. and this has been going on for 6 
months without any commit at all..
(I know this is stupid, but it was a bug in the application that caused the 
commit not to fire when it should)

>
>>
>> Can anyone smart confirm if there will be a problem if data isn't
>> commited often?
>
> There can be problems, depending on your transaction volume and whether
> you are performing a a lot of updates and deletes or not but this will
> not cause data to disappear.

Well, all data was lost.. and there was lots of updated data into several 
tables for a 6 months period.
When the application was terminated and the code (see above) was called, the 
data was never commited correct and all the data was lost.

>
> -- 
> Bill Todd (TeamB)
>