Defaults in enums don't work with ORACLE
Reported by Ulrich Kramer | July 9th, 2010 @ 01:33 AM
property :test, Enum[ :t1, :t2, :t3], :default => :t1
yields to an error, when the table is created, because enums are mapped to numbers, but the default is gives an a string..
Comments and changes to this ticket
-
Dan Kubb (dkubb) September 2nd, 2010 @ 01:22 PM
- State changed from “new” to “resolved”
(from [27c750636cbb9eec00fc0b75a0c1735deb4643bd]) Fixed default values to pass through Property#dump for DDL statements
- This fixes various problems with Flag and Enum properties, among others, where the value that is provided in the :default option was used directly in the DDL statement. While this works when the ruby value maps onto the database column type, it does not work when Property#dump converts the value into another representation.
[#1306 state:resolved] [#1320 state:resolved] [#1356 state:resolved] http://github.com/datamapper/dm-migrations/commit/27c750636cbb9eec0...
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 »
People watching this ticket
Ulrich Kramer
Referenced by
-
1356
Defaults in enums don't work with ORACLE
[#1306 state:resolved] [#1320
state:resolved] [#1356 stat...
-
1320
Using default values with Enum
[#1306 state:resolved] [#1320
state:resolved] [#1356 stat...
-
1306
auto_upgrade for Enum/Flag proporties fails
[#1306 state:resolved] [#1320
state:resolved] [#1356 stat...