Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Fix the MySQL column type `SET` registration bug | Taishi Kasuga | 2015-06-20 | 1 | -0/+4 |
| | |||||
* | fix MySQL enum type lookup with values matching another type. Closes #17402. | Yves Senn | 2014-10-29 | 1 | -0/+4 |
| | | | | | | | | | | The MySQLAdapter type map used the lowest priority for enum types. This was the result of a recent refactoring and lead to some broken lookups for enums with values that match other types. Like `8bit`. This patch restores the priority to what we had before the refactoring. /cc @sgrif | ||||
* | Delegate `Column#type` to the injected type object | Sean Griffin | 2014-05-19 | 1 | -0/+61 |
The decision to wrap type registrations in a proc was made for two reasons. 1. Some cases need to make an additional decision based on the type (e.g. a `Decimal` with a 0 scale) 2. Aliased types are automatically updated if they type they point to is updated later. If a user or another adapter decides to change the object used for `decimal` columns, `numeric`, and `number` will automatically point to the new type, without having to track what types are aliased explicitly. Everything else here should be pretty straightforward. PostgreSQL ranges had to change slightly, since the `simplified_type` method is gone. |