I haven’t decided yet whether to use schema shell or migrations. There’s also a descendant of Joel Moss’s migrations that includes YAML generation:
http://bakery.cakephp.org/articles/view/cakephp-yaml-migrations-and-fixtures-without-pear

I’m not sure what you mean with “unless schema can also move rows from tables”, though as far as I know (I don’t use the schema script myself) the schema tool is only about structure and not about data. Maybe you can use the “after”-callback method for this purpose?

When I put the site live, I manually added the SQL data into the database from a PHPMyAdmin dump file.

Now, if I do a schema update, it seems to want to change every column in every database – to an identical field name and type.

Update ends like this:
Updating Database…
activities: 1060: Duplicate column name ‘id’
…
…
activities: 1060: Duplicate column name ‘id’

(There is one of these ‘duplicate column’ messages for each DB table)

The question is – should I have used the ’schema create’ command to put the DB tables onto my production server? If so, that’s all well and good, but I’d still need to have a patch file populate with the initial row data – unless schema can also move rows from tables?

You can provide a schema name when you run ’schema run’: ‘cake schema run update your_schema’

Hope that helps!

However, when I add the schema.php to my GIT repository and push to my live server, I get the message: “Error: schema.php could not be loaded”.

Exploring the problem further, I tried to generate a schema.php file on my live server – this worked fine.

Comparing the two generated files, I think it’s got something to do with the way schema.php is generated – my local schema.php has the class name of ‘TestAppSchema’ whereas the one generated on my live server is ‘HttpdocsSchema’. Clearly, it’s using the name of the App root folder as the class so my question is:

How can I get the class to be consistent so that the ‘cake schema run update’ command works in different environments?

As far as I understand the schema script it is only for managing schema changes, and so I think that what you try to accomplish is not supported by the schema script…

nice tutorial for cake migrations but is there any way that i can insert some sample data into database with tables using the schema i tried a lot inserting queries in schema.php but no use its creating a table of that query.

i need some default data to be inserted into database when i create the tables using schema.

like in users table it create with name username and passwords as fields and as well as i want to insert data into the table

username password

xyz 123456
abc xyz123

like this?how can i do it using schema i know how to perform the above action using YAML file i have done but i want to do it using schema file?how

pls help? i think this is the feature which is lacking in shell??

Then I did some digging around in the code and found that the problem was that the postgres and mysqli drivers don’t override the alterSchema method which is responsible for generating the SQL for altering the schema.

Maybe I’ll do it, its quite a simple function in the mysql driver so shouldn’t be too difficult to do but for now I’m glad I got to the bottom of that one!