Migrations Schema Mods

[ghost]

Change the Migrations schema_version table so that it uses a table record rather than a table column per migration type.

[bencevans]

And is it worth removing the row/entry if the version equals 0?

[ghost]

Yeah that's a good idea.

[Icehawg]

Yes. This.

[ci-bonfire]

Yes. Sounds good.

[ghost]

Moving this to 0.3

[ghost]

I'll take this on.

I've most of it worked out now, just need to work on the migration file to move the data into the new structure.

[ghost]

Hey all - this is a big change - I've merged it into the develop branch so if you could test it would be great. This affects the Module Builder too but I think I've covered it.

Thanks

[przemeq]

I get an error when I try to install Bonfire now (version ci-bonfire-Bonfire-v0.2.1-13-g9bd89bf)

Fatal error: Call to a member function add_key() on a non-object in /blab/bonfire/application/core_modules/migrations/libraries/Migrations.php on line 151

[przemeq]

It is new fresh installation

[ghost]

@przemeq Thanks for reporting and sorry for the mistake. It should be resolved now.

[przemeq]

@seandowney

now when I try to install ci-bonfire-Bonfire-v0.2.1-14-gb176449 I get:

A Database Error Occurred
Error Number: 1054
Unknown column 'core' in field list
INSERT INTO bf_schema_version VALUES ('type', core);
Filename: /blab/db/migrations/core/012_Migration_schema_change.php
Line Number: 44

[ghost]

@przemeq Thanks again - someone had reported this on the forums also. This is resolved now.

The 012 migration file was only required for existing installations and not for during the installation process.

Sorry about that.

[przemeq]

you are welcome ;)