CakePHP & Migrations as Core

[Richard Sbresny]

Hey,

After using schema migrations on another framework I can easily see
the benefit of ensuring schema changes between team members are
identical.
Would love to see this a core feature going forward with CakePHP 2.

Thanks,
Richard

[Ceeram]

https://github.com/CakeDC/migrations like that you mean?

Op dinsdag 8 mei 2012 04:23:42 UTC+2 schreef VoiDeT het volgende:

[José Lorenzo Rodríguez]

He means exactly that one, but as part of the core. I don't think it is a crazy idea, it surely creates more things to maintain and develop but definitely would hep developers do their job, most frameworks already bundle that by default.

[Cauan Cabral]

Sure. With 56 forks, 153 watchers, 2 years and many other users I think CakeDC Migrations are ready to bundle with CakePHP core.

--

Cauan Cabral
----------------

Como falar comigo: Google Talk: cau...@gmail.com Skype: CauanCabral MSN: cau...@gmail.com

Onde me encontrar:

[Renan Gonçalves]

I strongly believe it should be part of the core.

In matter of fact, when I was working on it, still on CakeDC, I already developed it thinking in one day bundle it with the core. That's why its so dependent on the CakeSchema, for example.

The decision is not mine, but for me is a +1

--
Renan Gonçalves aka renan.saddam
Software Engineer at TrueServer B.V.
CakePHP Core Developer
Website: renangoncalves dot com
Amsterdam, The Netherlands

[José Lorenzo Rodríguez]

+1 too

[mark_story]

I'd like to see CakeSchema greatly improved before we go forward with adding migration support.  Currently CakeSchema has a pretty anemic set of types to choose from.  I'm really hoping we can address this in 3.0 and the model rewrite.  Not having access to things like big int or decimal types from migrations is a pretty big limitation for some applications.

Outside of the faults of CakeSchema, I'm in favour of eventually merging in a migration tool.  The CakeDC one seems to be the leader as far as current implementations goes as well.

-Mark

[Andy Hobbs]

I'll +1 Mark's comments :-)

It is a big issue for me that there is no support for fixed length strings in CakeSchema as generally I don't use varchar or equivalent unless I really have to.

[William Golden]

I agree, it's one of the CakeDC plugins that I use on each of my projects and merging it into the core would be awesome.

[Graham Weldon]

If a solution is bundled with the core, I would anticipate some more generic features:

 

- Support for any DB Engine

- Support for specific data types

I think Andy mentioned a simpler SQL script runner as opposed to an abstracted system.

This would allow things like stored procedures and triggers, and other non-column features to be included in a migration strategy.

 

Cheers,
Graham Weldon
http://grahamweldon.com
e. gra...@grahamweldon.com
p. (+61) 0407 017 293

Skype: grahamweldon

[mark_story]

+1 to just running SQL.  Routinely at $dayjob we have to do complex write behind migrations to alter tables with a lots of data and lots of IO with 0 downtime.  The only way that's possible is by allowing pure SQL migrations.

-Mark

[Graham Weldon]

+1

Cheers,

Graham Weldon

http://grahamweldon.com

e. gra...@grahamweldon.com

p. (+61) 0407 017 293

Skype: grahamweldon

[jeremyharris]

I'd love to see this as well, and plain old SQL would reduce headaches on the dev end and work on the core team end.