# Data in REAL database, instead of tags?

**URL:** <https://community.mp3tag.de/t/data-in-real-database-instead-of-tags/49914>\
**Category:** Off-Topic\
**Created:** [August 15, 2020, 7:46pm UTC](https://community.mp3tag.de/t/data-in-real-database-instead-of-tags/49914 "2020-08-15T19:46:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![incifinci](https://community.mp3tag.de/user_avatar/community.mp3tag.de/incifinci/32/6526_2.png) [@incifinci](https://community.mp3tag.de/u/incifinci)\
**Post date:** [August 15, 2020, 7:46pm UTC](https://community.mp3tag.de/t/data-in-real-database-instead-of-tags/49914/1 "2020-08-15T19:46:15Z")

</div>

I thought, it would be interesting and great to store my music data in a real database (like MySQL). In separate tables author, his nationality and life, work, presentation of the work, orchestra, conductor, his life and career, publisher, its characteristics, and so on. There would be no need to copy, it would be enough to simply enter (=select) the links to tables, when entering a new piece of music into my phonoteca, as it described in The Big Book, how a database works.

The **only** advantage of the data storage in the file, is portability. But it also has many drawbacks; especially the loss of time.

Now, if I want to enter the next performance of Tchaikovsky's Capriccio italiano:

**1. Export** of the existing one interpretation's data:

> $filename($getEnv('USERPROFILE')'\Desktop\aaa.txt',utf-8)$loop(1)If opus is the same\<\<\<+++\>\>\>%album%\<\<\<+++\>\>\>%albumfake%\<\<\<+++\>\>\>%tracktotal%\<\<\<+++\>\>\>$replace($meta\_sep(composer,\\), / ,\\)\<\<\<+++\>\>\>$replace($meta\_sep(arranger,\\), / ,\\)\<\<\<+++\>\>\>$replace($meta\_sep(lyricist,\\), / ,\\)\<\<\<+++\>\>\>%track%\<\<\<+++\>\>\>%title%\<\<\<+++\>\>\>%titlefake%\<\<\<+++\>\>\>%year%\<\<\<+++\>\>\>%contentgroup%\<\<\<+++\>\>\>%subtitle%\<\<\<+++\>\>\>$meta\_sep(genre,\\)\<\<\<+++\>\>\>$meta\_sep(language,\\)\<\<\<+++\>\>\>$meta\_sep(tagtechinfo,\\)\<\<\<+++\>\>\>%initialkey%\<\<\<+++\>\>\>%multitrack%\<\<\<+++\>\>\>$replace(%comment%,$char(9),\<u\>,$char(13)$char(10),\<s\>)\<\<\<+++\>\>\>$replace(%unsyncedlyrics%,$char(9),\<u\>,$char(13)$char(10),\<s\>)\<\<\<+++\>\>\>$replace(%cue%,$char(9),\<u\>,$char(13)$char(10),\<s\>)  
> $loopend()

**2. Import** Desktop\aaa.txt:

> If opus is the same\<\<\<+++\>\>\>%album%\<\<\<+++\>\>\>%albumfake%\<\<\<+++\>\>\>%tracktotal%\<\<\<+++\>\>\>%composer%\<\<\<+++\>\>\>%arranger%\<\<\<+++\>\>\>%lyricist%\<\<\<+++\>\>\>%track%\<\<\<+++\>\>\>%title%\<\<\<+++\>\>\>%titlefake%\<\<\<+++\>\>\>%year%\<\<\<+++\>\>\>%contentgroup%\<\<\<+++\>\>\>%subtitle%\<\<\<+++\>\>\>%genre%\<\<\<+++\>\>\>%language%\<\<\<+++\>\>\>%tagtechinfo%\<\<\<+++\>\>\>%initialkey%\<\<\<+++\>\>\>%multitrack%\<\<\<+++\>\>\>%comment%\<\<\<+++\>\>\>%unsyncedlyrics%\<\<\<+++\>\>\>%cue%

**3. Correct back** with Action Group (comment, unsyncedlyrics, cue)  
`$replace(%unsyncedlyrics%,<s>,$char(13)$char(10),<u>,$char(9))`

**4. Manually rewrite** : album, artist, conductor, times (performingdate, albumdate, publishingdate), and so on.

**Toooooo slow.** ☹  
And even more time, if I have to bring in first time some other opus' performance.

But either foobar2000 is not prepared for using database...  
Hmm... **Some program, that able** to convert data, created using database, into tags?? would be niiiiiice.

_(Oh, dear, why not BB codes in forum, with [code]here goes[/code]? This is catastrophic. Again: time, time, time...)_

---

<div class="post-metadata">

**Author:** ![LyricsLover](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)\
**Post date:** [August 15, 2020, 10:37pm UTC](https://community.mp3tag.de/t/data-in-real-database-instead-of-tags/49914/2 "2020-08-15T22:37:18Z")

</div>

Instead of reinvent the wheel you could use some (nearly) ready-to-use solution like:

[https://musicbrainz.org/doc/MusicBrainz\_Server/Setup](https://musicbrainz.org/doc/MusicBrainz_Server/Setup)

But be warned: Unless you have hundreds of thousands of tracks, a database is not faster then Mp3tag - believe me .-)

---

<div class="post-metadata">

**Author:** ![incifinci](https://community.mp3tag.de/user_avatar/community.mp3tag.de/incifinci/32/6526_2.png) [@incifinci](https://community.mp3tag.de/u/incifinci)\
**Post date:** [August 15, 2020, 10:55pm UTC](https://community.mp3tag.de/t/data-in-real-database-instead-of-tags/49914/3 "2020-08-15T22:55:29Z")

</div>

[LyricsLover](https://community.mp3tag.de/u/LyricsLover), thank you for your quick and valuable answer. It seems to bee, what i want as a workaround.

Unfortunately, of course, such a solution (with a connector) also has its downsides: the data, updated in the database, does not go into the existing tags.

And yes, you are right:

> [@LyricsLover](#):
>
> Unless you have hundreds of thousands of tracks, a database is not faster then Mp3tag.

(I mean, if simply, with connector.)