Hi Martin,
I can not agree with you.
Good commercial database application must be reliable. NO ONE need corrupted indexes, a lost memo, inconsistent data, etc. As as developer I can say also that I do not need taking time phones from angry customers even "unimportant" one.
I understand that it is all about acceptable level of reliability - probably you and I define it in different way.
>Hi, Josef.
>
>>I wonder what kind of database applications does not need reliability.
>>IMHO there is no such animal.
>
>The ones where high reliability costs more than the value the application produces, IMHO. That's key in choosing DBFs over an industrial-strenght database.
>
>In a small shop where having corrupted indexes, a lost memo, inconsistent data, etc, is not a big problem and going back to a day-old backup is enough, DBFs can o the job at a very low cost.
>
>In mission critical systems where stopping the application means start loosing money, any database engine pays for itself preety quickly.
>
>My 2 cents,
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only