Metdata Integrity, Tag files vs. DB only? Options

[topdownjimmy]

I'm becoming increasingly concerned with the integrity of my metadata, and all the talk about "changing files every time you play them is bad" is getting to me. I'd like to keep everything that isn't inherent to the song in the DB, but also be sure that all the information relevant to the song is stored within the file itself.

As a possible solution: would setting foobar to write ID3v1 tags only do what I desire? I'm thinking this will work because ID3v1 only has so many fields, so %play_counter% and %rating% will be restricted to the DB, but if I realize that my %album% field had a typo in it, any changes I make will be reflected within the file in addition to the DB. Am I correct in thinking this? How am I even able to tell whether metadata is in the file or just the DB?

[gob]

Right now i have all of my rating, play counter, and etc. stored in tags. is there a way for me to transfer these values to the database and delete the tags? i really dont like storing this info in the files.

[mazy]

Right now i have all of my rating, play counter, and etc. stored in tags. is there a way for me to transfer these values to the database and delete the tags? i really dont like storing this info in the files.

that's not really possible atm. my repost from another forum:

... you would need changes in the core for that and that's what i hope for in 0.9 ...

the only thing (or two) i can think off would be this hack-ish approach:

1) block all tag operations and make plugin, which would monitor changes to db (not sure there's a callback for that - that's the problem) and propagate changes to some 'allowed' tags to the files. there would be these problems:
1.1) not sure there's a callback for db change
1.2) plugin would have to handle writing of the tags itself (for all formats of files, all formats of tags etc.)
1.3) there could be issues as how to read these tags back etc. (my scenario: plugin would update the file, foobar would notice that because of timestamp or filesize change and re-read these tags back from file to db, deleting all extra-db tags)
1.4) other problems

2) make plugin that would provide service to others to read / write tags for given metadb handle from external db (mysql, txt, whatever ...). problems:
2.1) plugins would have to be updated to support this
2.2) there could be overkill (i.e. mysql would have to be instaled etc.)

so as much as i would love this, it's something we better have to wait for to be addressed in the core ...