On 14/09/12 20:07, Ludo Brands wrote:
It is already quite a useful component as is. Since you are FBAdmin's
author, and are knowledgeable in the service API, what do you
recommend
regarding the non basic admin actions? Forced Writes in particular is
interesting as it might have to be turned off when pumping
data for example.
As said before IMHO forced writes doesn't belong in a component that comes
standard with Lazarus. Google for Firebird forced writes off and you get as
first page http://www.firebirdsql.org/manual/qsg2-safety.html chapter "how
to corrupt a database". Forced Writes is a speed hack that turns off
effectively the database integrity for the time of the operation. That is
integrity in the largest sense. When something goes wrong, your complete
database can become unusable.
+1
My question was more geared towards an extension to FBAdmin, or an
entirely different component such as FBServices which is derived from
FBAdmin.
Unless you are writing a db admin tool or a
very specialised tool, no business application should use this.
A corner case which could benefit from Forced Writes off, almost risk
free: Data is pumped into a freshly created FB database, report tables
are created and populated, then used for reporting purposes. Then the
whole thing is discarded.
Stephano
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
