CodeIgniter Forums
Migration Methods - Printable Version

+- CodeIgniter Forums (https://forum.codeigniter.com)
+-- Forum: CodeIgniter 4 (https://forum.codeigniter.com/forum-28.html)
+--- Forum: CodeIgniter 4 Discussion (https://forum.codeigniter.com/forum-31.html)
+--- Thread: Migration Methods (/thread-73376.html)



Migration Methods - MGatner - 04-17-2019

CI4 currently supports two different naming formats for migration files, sequential (001, 002, 003) and timestamp (20190417134413):
https://codeigniter4.github.io/CodeIgniter4/dbmgmt/migration.html#migration-file-names


Sequential was a backwards-compatible addition to CI3 - should it continue into CI4? Check out this thread for an example of one of the limitations this might pose:
https://forum.codeigniter.com/thread-73375-post-363511.html


RE: Migration Methods - dave friend - 04-17-2019

Would it be useful/interesting to add a "Don't Care" option to the poll?


RE: Migration Methods - orionstar - 04-18-2019

Timestamp based can be problematic if your team is working in multiple time zones, so I think the sequentual is a must have!


RE: Migration Methods - kilishan - 04-18-2019

(04-18-2019, 01:47 AM)orionstar Wrote: Timestamp based can be problematic if your team is working in multiple time zones, so I think the sequentual is a must have!

I think we can overcome that concern by forcing all timestamps generated through the cli method to be in UTC. Then won't matter where you live and teams should be able to all use it just fine, right?


RE: Migration Methods - puschie - 04-24-2019

we use sequential migration for client migration and timestamp for dev migration
-> the client migration order is different because some features are not published yet ( but already have migration for it ).


RE: Migration Methods - orionstar - 04-24-2019

(04-18-2019, 09:23 PM)kilishan Wrote:
(04-18-2019, 01:47 AM)orionstar Wrote: Timestamp based can be problematic if your team is working in multiple time zones, so I think the sequentual is a must have!

I think we can overcome that concern by forcing all timestamps generated through the cli method to be in UTC. Then won't matter where you live and teams should be able to all use it just fine, right?

Sounds good for me, thanks!