On 19 Aug 2009, at 11:17, Tom Hughes wrote:
On 19/08/09 11:12, Shaun McDonald wrote:On 19 Aug 2009, at 09:40, Tom Hughes wrote:On 19/08/09 09:22, Shaun McDonald wrote:Thanks for alerting me to this problem. It was caused by TomH zapping the migration files in the previous revert and there being no automaticway to do the down migrations when this happens.Do what? I didn't zap any migrations...http://trac.openstreetmap.org/changeset/16070Unfortunately I hadn't zapped the tables/undone the migrations when youhad done the revert, so in reality my fault.Oh, way back then... Several migrations have gone in since then though, did it not throw a wobbly over them?
I've checked postgres and all migrations since the I18n import and they seem to all be there, so I must have removed the migration numbers from the table, but not undone the tables creation.
MySQL is fine up to the last migration with the foreign keys where it is giving an error that I don't understand:
ad...@smcdonald:~/.cruise/projects/osmapi-mysql/work$ rake db:migrate (in /srv/.cruise/projects/osmapi-mysql/work)== AddForeignKeysToOauthTables: migrating ====================================
-- add_foreign_key(:oauth_tokens, [:user_id], :users, [:id]) rake aborted! An error has occurred, all later migrations canceled:Mysql::Error: Can't create table './openstreetmap/ #sql-16ef_2276.frm' (errno: 150): ALTER TABLE oauth_tokens ADD FOREIGN KEY (`user_id`) REFERENCES users (`id`)
(See full trace by running task with --trace) Shaun
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
