diff options
author | Sean Griffin <sean@thoughtbot.com> | 2015-01-24 21:07:55 -0700 |
---|---|---|
committer | Sean Griffin <sean@thoughtbot.com> | 2015-01-24 21:07:55 -0700 |
commit | 3327cd3f61a22a5834dcbf9bd24ecbc3a23de3de (patch) | |
tree | 7b8ce77b5bbf685ee7b09d2e09d3c67292229491 /guides/source/4_0_release_notes.md | |
parent | ae8cd56c7b1f3130eb3b8f2632a528a8fc78e56c (diff) | |
download | rails-3327cd3f61a22a5834dcbf9bd24ecbc3a23de3de.tar.gz rails-3327cd3f61a22a5834dcbf9bd24ecbc3a23de3de.tar.bz2 rails-3327cd3f61a22a5834dcbf9bd24ecbc3a23de3de.zip |
Expand the number of types which can use prepared statements
This will allow all types which require no additional handling to use
prepared statements. Specifically, this will allow for `true`, `false`,
`Date`, `Time`, and any custom PG type to use prepared statements. This
also revealed another source of nil columns in bind params, and an
inconsistency in their use.
The specific inconsistency comes from a nested query coming from a
through association, where one of the inversed associations is not
bi-directional.
The stop-gap is to simply construct the column at the site it is being
used. This should simply go away on its own once we use `Attribute` to
represent them instead, since we already have all of the information we
need.
Diffstat (limited to 'guides/source/4_0_release_notes.md')
0 files changed, 0 insertions, 0 deletions