This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
We found two situations where Lightspeed cannot write data to database (SQLite) and it is very hard to debug/find:
In both cases errors are very hard to find, since we cannot see the incorrect SQL command (in SQLite). The exception is as follows (for 2nd case): System.Data.SQLite.SQLiteException was unhandled by user code
It would be great if Lightspeed caught such exception and thrown an aggregate exception showing the original exception with its stack trace, but also showing the SQL command. |
|
|
You can use LightSpeedContext.Logger to view the generated SQL. This should work even if the SQL itself results in an error. See Help Topics > LightSpeed > Logging in the docs for more info. |
|