Migrating Migrations Table from CI3 for existing databases |
(02-03-2023, 12:50 AM)kenjis Wrote:(02-02-2023, 11:24 PM)objecttothis Wrote: It would be nicer if migrate recognized the version number from CI3 migrations and didn't try to run migrations before that. This is an interesting idea. No, I don't think there is a need to revert once a migration has run. I could programmatically: - Check the CI3 version in the database. - delete all migrations files to that point. - drop the old table. - Run CI4 migrations. The only potential hiccup I can see is needing to have write access to that folder from the PID running php. |
Messages In This Thread |
Migrating Migrations Table from CI3 for existing databases - by objecttothis - 02-02-2023, 01:59 PM
RE: Migrating Migrations Table from CI3 for existing databases - by kenjis - 02-02-2023, 05:24 PM
RE: Migrating Migrations Table from CI3 for existing databases - by objecttothis - 02-02-2023, 10:55 PM
RE: Migrating Migrations Table from CI3 for existing databases - by kenjis - 02-02-2023, 11:16 PM
RE: Migrating Migrations Table from CI3 for existing databases - by objecttothis - 02-02-2023, 11:24 PM
RE: Migrating Migrations Table from CI3 for existing databases - by kenjis - 02-03-2023, 12:50 AM
RE: Migrating Migrations Table from CI3 for existing databases - by objecttothis - 02-03-2023, 12:57 AM
RE: Migrating Migrations Table from CI3 for existing databases - by kenjis - 02-03-2023, 12:44 AM
|