Maikel Linke
301add4992
Remove faulty migration generation
...
The long timestamps don't play well with Rails default timestamps for
migrations. They are always seen as the newest. Not using long
timestamps leads to duplicate timestamps though.
The better solution is to use `rails generate migration` and copy the
`change` method.
2024-01-15 14:36:23 +11:00
..
2023-11-30 13:47:39 +11:00
2023-09-16 09:05:31 +09:00
2024-01-08 13:01:21 +11:00
2024-01-08 11:32:01 +11:00
2024-01-08 13:01:21 +11:00
2023-07-18 08:17:34 +09:00
2023-11-17 09:41:44 +11:00
2023-12-22 13:20:14 +01:00
2023-12-21 15:09:09 +11:00
2024-01-12 12:12:17 +00:00
2023-11-30 20:32:23 +00:00
2023-09-21 22:58:42 +09:00
2024-01-15 14:36:23 +11:00
2023-11-10 09:13:57 +09:00
2024-01-08 13:17:29 +01:00
2024-01-08 15:53:50 +11:00
2023-12-01 11:32:55 +00:00
2023-09-25 13:15:38 +09:00
2024-01-03 11:34:57 +01:00
2024-01-08 13:01:21 +11:00
2024-01-11 09:04:49 +11:00
2022-05-12 16:54:13 +02:00
2023-12-01 11:32:55 +00:00
2023-12-28 17:47:09 +11:00
2023-08-08 11:36:31 +01:00
2023-08-15 08:36:22 +02:00
2023-11-23 17:00:44 +11:00
2024-01-11 15:13:41 +11:00
2023-12-22 13:20:14 +01:00