I am building a new API over a legacy database, so there's a mix of preexisting tables with new tables I'm setting up from scratch. I'm trying to use Schema Builder and migrations for the new tables.
I notice some of the artisan:migrate commands become overly destructive in this use case (such as migrate:fresh drops all tables, encompassing preexisting which I can't easily get back, likely assuming that the database is solely for use of the framework).
My ?'s are: What's the best way to manage this? Simply don't use migrate:fresh? Should I not be using these built-in's? Should I create a database exclusively for Laravel (and handle connection with something like Schema::connection('whatever')) - with my legacy db for supplemental data? etc.
We usually do migrate:fresh when the app is still on the dev or when it's on the first run on the production. Given that you have created proper migrations, calling artisan migrate can still do its job even if there is an preexisting db resources.
For instance, you have new tables, artisan migrate is good to go command.
Another 1, if you got new column for an existing table, given u have a proper migration for this, artisan migrate is applicable too.
Thank you!
Please or to participate in this conversation.