Support the ongoing development of Laravel.io →
Configuration Database
Last updated 7 months ago.
0

Gatix said:

Try this:

https://github.com/Xethron/migrations-generator

Looks like Github Xethron/migrations-generator is appealing and stands on giants shoulder (see related composer file for more details)!

Last updated 7 years ago.
0

you don't have to use migrations. It's just a tool and it's up to the user to use it or not.

By default the timestamps created_at and updated_at are set.

Even if you use migration you don't necessarily want them to be added to each table because they might not make sense (eg pivot tables).

You can disable the setting of the timestamps by adding to your/each Model class:

public static $timestamps = false;
Last updated 7 years ago.
0

Ok.

I couldn't get the other solution to work but for my project I don't think it's necessary.

On my next project I will try them out from the start to learn more about them.

Thanks for your help people.

frezno said:

you don't have to use migrations. It's just a tool and it's up to the user to use it or not.

By default the timestamps created_at and updated_at are set.

Even if you use migration you don't necessarily want them to be added to each table because they might not make sense (eg pivot tables).

You can disable the setting of the timestamps by adding to your/each Model class:

public static $timestamps = false;
0

Sign in to participate in this thread!

LoadForge

Your banner here too?

Moderators

We'd like to thank these amazing companies for supporting us

Your logo here?

Laravel.io

The Laravel portal for problem solving, knowledge sharing and community building.

© 2022 Laravel.io - All rights reserved.