Well here's the deal... I played around with Schema a bit last night. I have only a few issues with it in practice:
1. It doesn't handle autoincrement correctly in the latest nightly build when you generate a schema from an existing table. 2. The downloadable 1.2 beta has major bugs in it like an incorrect refernce to the string tokenizer so newbies may not even be fully exploring Schema in the console! Aside from that... You can basically use the schema tool as migrations. You can create Schema.php and then create Schema_2.php and so on. You're then able to note version numbers you want to "migrate" to in the console. So far as I can tell, it has a lot in common with the old way that migrations worked in Rails 2.0. Given that this is now how Schema works I think it may be worthwhile to investigate different ways to use Schema. Dardo has one methodology that he's been evangelizing in this thread. I wonder if we could get phpNut or someone on the core team more familiar with Schema's development to comment on the design decisions behind it given the functionality that hasn't been talked about on here. I'll probably put together a little tutorial or something for my blog once I get everything all worked out on my own, but this was news to me! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
