Hi, I am creating some database migrations for cities and states in Laravel, they both have the created_at, and the updated_at fields, now I am trying to fill in those using an SQL script that I have found online, this is the way I will be able to do it , so My Question: is it OK if I leave them empty, and whether in any case I will have some issues if I leave them empty now, my web application is expected to scale in the future.
you don't need them, they are there for you use, so you can add to your model class public $timestamps = false;, or but if your using a model etc these normally fill in automatically anyways, so you dont need to try or add then in your entry code.
For tables that don't need timestamps, don't add $table->timestamps(); to your migration. If you don't add them, you must do as @simondavies says and add public $timestamps = false; to the model. If you don't use Eloquent at all and don't define a model, just don't add the timestamps. Finally, don't just copy/paste SQL you find on the internet to make your app work. Eloquent is a wonderful thing, watch the casts here and learn how to use it. IMHO, copy/paste doesn't scale--knowledge does.
thank you @lindstrom , I just copied the list of cities, countries and states, the actual names for the whole world, I don't think this will be bad for my app, because the code is just INSERT INTO blabal blabl VALUES blabla, ti does not contain actually any logic or relationships, those I did myself using Eloquent, I thik this is OK, but I still a beginner with Laravel so if there is any thing wrong with it please tell me about .
@esdairi Ah, ok--gotcha. If it's a new app, you could load the data in a migration. If you have a csv, for example, you could try it this way: https://tenerant.com/blog/using-load-data-local-infile-in-a-laravel-migration/
Alternatively, you could do it with a seeder. The advantage to the migration method is as you are building you can rollback or reset and rebuild all you like.
@lindstrom thanks, this will be so helpful for me, thanks again.
Please or to participate in this conversation.