I'm getting into web development, and I'm trying to get a grip on databases.
In an app I want to make, there is a read only database that will be filled up with a large amount of data, which will be the heart of the application, and also a lot of work to put in.
I'm uncomfortable with putting all this data into the database, as the database is "separate" from my web app code. I feel like I should rather write my data in code somewhere, and then have my application put the data into the database for me.
This way I would have my entire project written in code, and not an integral part of my software hidden away in the database, which is a bit complicated to work with, and seems difficult to move from computer to computer.
But is this a sensible way to do this, however? Should I write my data in code, and every time I launch the server, make the application drop all the tables and read them in from my code again?
Is this the wrong way to go about it? Would it cause considerable overhead? How do people do this?