I think the risk is that 7.9 and 7.8 diverge in terms of what the database and settings do. The reason for this is that upgrades are intended to be handled ok, but downgrades are not - so it depends what 7.9 is doing differently whether this is ok or not.
The difference between 7.8/7.7 and 7.9 is the addition of the library_track table. None of the existing tables has been changed (nor indices fwiw). Up/downgrade should work just find.
But - as with all schema changes - whenever you switch between the two, a full wipe & rescan will be triggered. Even though 7.8 could easily handle the 7.9 database, ignoring the new table. But that's how the schema up/downgrade mechanism works.
I'm switching several times a week, though not on my main system. But besides the scan needed it should work just fine.
-- Michael _______________________________________________ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
