Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Remove AR Properties from the public API | Sean Griffin | 2014-05-27 | 1 | -1/+1 |
| | | | | | Making this part of the public API was premature, let's make it private again while I continue to work on the surrounding code. | ||||
* | Add a public API to allow users to specify column types | Sean Griffin | 2014-05-26 | 1 | -1/+1 |
| | | | | | | | | | | | | | | | | | | | | | | | | As a result of all of the refactoring that's been done, it's now possible for us to define a public API to allow users to specify behavior. This is an initial implementation so that I can work off of it in smaller pieces for additional features/refactorings. The current behavior will continue to stay the same, though I'd like to refactor towards the automatic schema detection being built off of this API, and add the ability to opt out of automatic schema detection. Use cases: - We can deprecate a lot of the edge cases around types, now that there is an alternate path for users who wish to maintain the same behavior. - I intend to refactor serialized columns to be built on top of this API. - Gem and library maintainers are able to interact with `ActiveRecord` at a slightly lower level in a more stable way. - Interesting ability to reverse the work flow of adding to the schema. Model can become the single source of truth for the structure. We can compare that to what the database says the schema is, diff them, and generate a migration. | ||||
* | Delegate `klass` to the injected type object | Sean Griffin | 2014-05-20 | 1 | -0/+4 |
| | |||||
* | Delegate predicate methods to injected type object on Column | Sean Griffin | 2014-05-20 | 1 | -0/+4 |
| | |||||
* | Delegate `#type_cast` to injected type objects on SQLite3 | Sean Griffin | 2014-05-20 | 1 | -0/+10 |
| | |||||
* | Delegate `Column#type` to the injected type object | Sean Griffin | 2014-05-19 | 1 | -0/+11 |
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. |