I’ve tried and I’ve tried (thanks Apple) to corrupt a Servoy solution and nothing has worked…
http://www.servoymagazine.com/home/2006 … _cras.html
This has got to be a bug.
Like the story , the credits actually must go to transactional databases, they make Servoy crash resilient.
BTW this is the only reason we require transaction support for the repository database.
There is a huge thread going on right now about corruption in Filemaker databases. How to detect it and how to correct it. Is there such a thread on this Servoy forum? How would we detect and correct corruption in our Sybase? Are there SQL utilities, common knowledge, rules of thumb, etc?
Thanks
Bill Belanger
Hi Bill,
As you probably know Servoy stores all the solution sources in a (SQL) back-end RDBMS (Relational Database Management System).
These RDBMSs by design make sure your data is written correctly or not at all. Even when a computer crashes during writing of data a RDBMS should keep the data integrity intact. Also by using transactions (what Servoy uses with the repository) it can rollback any updates/deletes/inserts when an error/crash/whatever occurs.
All this makes Servoy very robust what source corruption concerns.
Now there are other ways where your solution might get ‘corrupted’ (unlinked image media) is when using modules and exporting/importing a solution without the module with your image media.
But I believe that is all solved in the 3.1 branch.
Hope this helps.
A very interesting question. I’ve used FileMaker & Sybase SQL Anywhere side by side for about 8+ years, and after numerous crashes, have yet to see Sybase “corruption”
There is a Sybase “Validate” utility. See “ensuring your database is valid” in the Admin guide.
Sybase also offers an unload / reload utility, which FileMaker desperately needs