auto_upgrade! doesn't migrate String length
Reported by Roman | June 17th, 2009 @ 02:48 AM
When using auto_upgrade! length is not taken into account.
It can be non destructively upgraded under PostgreSQL (I do not
know about other dbs) using ALTER TABLE ALTER TYPE.
I attach an example which shows the problem.
Comments and changes to this ticket
-
Roman June 17th, 2009 @ 02:49 AM
- Tag set to “auto_upgrade, core, dm-core, migrations, postgres”
-
Dan Kubb (dkubb) June 17th, 2009 @ 03:04 AM
- Assigned user set to “Dan Kubb (dkubb)”
- State changed from “new” to “accepted”
- Milestone set to “0.10.1”
This is known, and something I would like to work on during the 0.10.x series.
Please see the roadmap for further details:
-
Dan Kubb (dkubb) October 4th, 2009 @ 09:33 PM
- Milestone changed from “0.10.1” to “0.10.2”
[project:id#20609 not-tagged:"0.10.0" not-tagged:"0.10.1" milestone:id#51895 bulk edit command]
-
Dan Kubb (dkubb) October 6th, 2009 @ 12:11 AM
- Milestone cleared.
- State changed from “accepted” to “suggestion”
- Assigned user cleared.
-
Piotr Solnica (solnic) May 17th, 2011 @ 02:33 AM
- Tag changed from “auto_upgrade, core, dm-core, migrations, postgres” to “auto_upgrade, dm-migrations, postgres”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Dan Kubb (dkubb)
Piotr Solnica (solnic)