IT Specialist ·

I am a Microsoft SQL Server programmer who is a bit out of practice. I have been asked to assist on a new project. The overall purpose is to organize a large number of recordings so that they can be searched. I have an enormous music library but my songs are several hours long. I need to include things like time, date and location of the recording. I don't have a problem with the general database design. I have two primary questions:

  1. I need to use either MySQL or PostgreSQL on a Linux based OS. Which would be better for this application?
  2. I have not dealt with a sound based data type before. How do I store that and put it in a table? Thank you.
READ LESS
7 upvotes·149.7K views
Replies (6)
Web Developer at Soltech LLC·

Hey Erin! I would recommend checking out Directus before you start work on building your own app for them. I just stumbled upon it, and so far extremely happy with the functionalities. If your client is just looking for a simple web app for their own data, then Directus may be a great option. It offers "database mirroring", so that you can connect it to any database and set up functionality around it!

READ MORE
3 upvotes·1 comment·74K views
Christopher Wray
Christopher Wray
·
March 12th 2020 at 5:10PM

Also, as far as postgre or mysql, goes.. I'm not sure if there would be a huge difference on a Linux machine in functionality or power.

·
Reply

Hi Erin,

Honestly both databases will do the job just fine. I personally prefer Postgres.

Much more important is how you store the audio. While you could technically use a blob type column, it's really not ideal to be storing audio files which are "several hours long" in a database row. Instead consider storing the audio files in an object store (hosted options include backblaze b2 or aws s3) and persisting the key (which references that object) in your database column.

READ MORE
7 upvotes·74.2K views
View all (6)
Avatar of Christopher Wray

Christopher Wray

Web Developer at Soltech LLC