Cleaning up the database?

[Spark]

Is there a good way to clean up the database? It seems, the bigger it gets, the more error prone it becomes.

Would be nice if the database was split from the config side, and the program side (recordings).

Once it becomes too big, then it doesn't start recording shows when it should, and I guess that is because there are errors in the database file.

[sub]

I cant say I've seen anything that makes me think the capture source configuration and recordings list should be in separate database files. I've not see any problems with large databases, and separating them would just make development awkward.

The next release is using an updated version of the SQLite database libraries, which may help with stability issues you're experiences.

[Spark]

I cant say I've seen anything that makes me think the capture source configuration and recordings list should be in separate database files. I've not see any problems with large databases, and separating them would just make development awkward.

The next release is using an updated version of the SQLite database libraries, which may help with stability issues you're experiences.

How large of a database have you tested? Mine seems to get corrupted after recording shows for 30-45 days of use.

If it is split up, then we don't have to redo the configuration again & again once the corruption happens. Though, right now, I have a backup of a "good" database, and just switch to that once it becomes corrupted.

[sub]

Mine seems to get corrupted after recording shows for 30-45 days of use.

We've been using the same database now for several years, and reports of corrupt databases a few and far between, so I dont think there is any common issue with this occurring.

If it is split up, then we don't have to redo the configuration again & again once the corruption happens.

I can understand why you'd want this change if you're having ongoing issues, but I really dont see this change happening. Too much work for me, would make stuff more awkward from a code perspective, and would break lots of plugins (including some where the developers are no longer here maintaining the plugin). Sorry.