I am in the process of updating some old code involving web apps that use SQLite databases, and I have a question. The old way of handling database errors was to do some database operation and then check the Error property of the database. At some point after I wrote the original code (I am not exactly sure when), that approach was deprecated in favor of using a try-catch structure to trap a DatabaseException.
The part that I don’t understand is how the original deprecated mechanism still works if the database is now raising exceptions instead of just setting some properties. It seems that I must must move to the new approach if I am using a modern version of Xojo to compile the app. But fixing this throughout the entire suite of applications would be a lot of work.
This is important because the code I am working on is used by other people, and must be robust. If the app fails because of unhandled exceptions, it will go offline, and no one will be able to use it.
Can anyone clarify whether the deprecated mechanism still works and if so, how?