aboutsummaryrefslogtreecommitdiffstats
path: root/activerecord/lib/active_record/connection_adapters/type
Commit message (Collapse)AuthorAgeFilesLines
* Move types to the top level `ActiveRecord` namespaceSean Griffin2014-05-2716-471/+0
| | | | | `ActiveRecord::ConnectionAdapters::Type::Value` => `ActiveRecord::Type::Value`
* Remove AR Properties from the public APISean Griffin2014-05-2710-10/+10
| | | | | 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 typesSean Griffin2014-05-2611-12/+21
| | | | | | | | | | | | | | | | | | | | | | | | 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.
* Remove checks against `column.type` in abstract adapter quotingSean Griffin2014-05-262-0/+4
| | | | | | The intention is to eventually remove `column` from the arguments list both for `quote` and for `type_cast` entirely. This is the first step to that end.
* Add an interface for type objects to control Ruby => SQLSean Griffin2014-05-261-0/+4
| | | | | Adds the ability to save custom types, which type cast to non-primitive ruby objects.
* Remove special case in schema dumper for decimal without scaleSean Griffin2014-05-231-0/+13
|
* Push limit to type objectsSean Griffin2014-05-221-2/+3
| | | | | Columns and injected types no longer have any conditionals based on the format of SQL type strings! Hooray!
* Push precision to type objectsSean Griffin2014-05-223-12/+3
|
* Push scale to type objectsSean Griffin2014-05-222-4/+7
| | | | | | Ideally types will be usable without having to specify a sql type string, so we should keep the information related to parsing them on the adapter or another object.
* Move `extract_precision` onto type objectsDan Croak and Sean Griffin2014-05-223-0/+11
|
* Allow additional arguments to be used during type map lookupsSean Griffin2014-05-222-9/+9
| | | | | | | | Determining things like precision and scale in postgresql will require the given blocks to take additional arguments besides the OID. - Adds the ability to handle additional arguments to `TypeMap` - Passes the column type to blocks when looking up PG types
* Move extract_scale to decimal typeSean Griffin2014-05-212-4/+3
| | | | | | The only type that has a scale is decimal. There's a special case where decimal columns with 0 scale are type cast to integers if the scale is not specified. Appears to only affect schema dumping.
* push `extract_scale` to the `Type`.Yves Senn2014-05-211-0/+4
| | | | | | | - `extract_precision`, `extract_limit`, and `extract_default` probably need to follow. - would be good to remove the delegation `Column#extract_scale`. /cc @sgrif
* Delegate `klass` to the injected type objectSean Griffin2014-05-208-0/+32
|
* Delegate `type_cast_for_write` to injected type objectSean Griffin2014-05-202-0/+13
|
* Merge pull request #15207 from sgrif/sg-inline-column-helpersRafael Mendonça França2014-05-207-6/+74
|\ | | | | Inline typecasting helpers from Column to the appropriate types
| * Inline typecasting helpers from Column to the appropriate typesSean Griffin2014-05-207-6/+74
| |
* | Merge pull request #15206 from sgrif/sg-type-map-postgresqlRafael Mendonça França2014-05-201-0/+6
|\ \ | | | | | | Use the generic type map for PostgreSQL OID registrations
| * | Use the generic type map for PostgreSQL OID registrationsSean Griffin2014-05-201-0/+6
| |/
* / Delegate predicate methods to injected type object on ColumnSean Griffin2014-05-207-0/+37
|/
* Use the generic type map object for mysql field lookupsSean Griffin2014-05-201-0/+15
|
* Delegate type_cast to injected type object in mysqlSean Griffin2014-05-203-0/+28
|
* Delegate `#type_cast` to injected type objects on SQLite3Sean Griffin2014-05-209-0/+62
|
* Remove :timestamp column typeSean Griffin2014-05-192-14/+1
| | | | | | | | | | | | The `:timestamp` type for columns is unused. All database adapters treat them as the same database type. All code in `ActiveRecord` which changes its behavior based on the column's type acts the same in both cases. However, when the type is passed to code that checks for the `:datetime` type, but not `:timestamp` (such as XML serialization), the result is unexpected behavior. Existing schema definitions will continue to work, and the `timestamp` type is transparently aliased to `datetime`.
* Delegate `Column#type` to the injected type objectSean Griffin2014-05-1913-0/+176
| | | | | | | | | | | | | | | | 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.
* Add a type object to Column constructorSean Griffin2014-05-171-0/+8
Part of #15134. In order to perform typecasting polymorphically, we need to add another argument to the constructor. The order was chosen to match the `oid_type` on `PostgreSQLColumn`.