Forum: Typo Mysql db migration jams up with Typo 5.4.4

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
69e61e9337179fd6a60e50f19c3f3a27?d=identicon&s=25 Simon Brown (Guest)
on 2010-04-23 23:20
(Received via mailing list)
> Cyril Mougel cyril.mougel at gmail.com
> Fri Apr 23 08:10:29 EDT 2010
>
> It's seems that this error because you don't starting your database by
> migration.
>
> Can you send us the result of :
>
> select * from schema_migrations;
>

Certainly. Now that you mention it, I did get an error about "typo has
already stopped.." or something along those lines. But that wasn't a
surprise, since it definitely wasn't working at the time (couldn't
restart after updating some gems).

Here's my results:


mysql> select * from schema_migrations;
+---------+
| version |
+---------+
| 84      |
+---------+
1 row in set (0.04 sec)


Simon
8f6b8e99f52f0928287b01a006950f52?d=identicon&s=25 Matijs van Zuijlen (mvz)
on 2010-04-24 10:29
(Received via mailing list)
Hi Simon,

On 04/23/2010 11:06 PM, Simon Brown wrote:
> mysql>  select * from schema_migrations;
> +---------+
> | version |
> +---------+
> | 84      |
> +---------+
> 1 row in set (0.04 sec)

That's definitely wrong. There should be an entry for each migration,
not just
the last one. If you insert one record for each migration number 1
through 83,
things should work fine again.

Regards,
This topic is locked and can not be replied to.