- 30 12月, 2014 1 次提交
-
-
由 Takashi Kokubun 提交于
-
- 29 12月, 2014 10 次提交
-
-
由 Yves Senn 提交于
adjust args of Bundler.require in guides [ci skip]
-
由 Yosuke 提交于
Arguments of Bundler.require of generator has been changed from rails4.0.4. https://github.com/rails/rails/blob/v4.0.4/railties/lib/rails/generators/rails/app/templates/config/application.rb#L16
-
由 Guillermo Iguaran 提交于
Expectation comes first
-
由 Yukio Mizuta 提交于
-
由 Robin Dupret 提交于
-
由 Guillermo Iguaran 提交于
Require Ruby 2.2 for Rails 5.0
-
由 Sean Griffin 提交于
Actually autoload all second-level directories called `app/*/concerns`
-
由 Yves Senn 提交于
-
由 Sean Griffin 提交于
Update example test documentation
-
由 Ben Prew 提交于
Example does not work with session headers, should use request headers. [ci skip]
-
- 28 12月, 2014 10 次提交
-
-
由 Guillermo Iguaran 提交于
Fix warning: `*' interpreted as argument prefix
-
由 Ryuta Kamizono 提交于
-
由 Sean Griffin 提交于
Provide :touch option to save() to accommodate saving without updating t...
-
由 Dan Olson 提交于
-
由 Sean Griffin 提交于
We only support classes which provide a no-args constructor to use as a default value. We can provide a more helpful error message if we catch this when `serialize` is called, rather than letting it error when you try to assign the attribute. Fixes #18224
-
由 Sean Griffin 提交于
Add bigint primary key support for MySQL.
-
由 Ryuta Kamizono 提交于
Example: create_table :foos, id: :bigint do |t| end
-
由 Ryuta Kamizono 提交于
-
由 Yves Senn 提交于
/cc @sgrif
-
由 Yves Senn 提交于
Most of the documentation very closely mirrors the matching docs from `SchemaStatements`. I reduced duplicated copy and added links to the underlying methods for the user to follow.
-
- 27 12月, 2014 19 次提交
-
-
由 Aditya Kapoor 提交于
[ci skip]
-
由 Sean Griffin 提交于
Refactor `PostgreSQL::TableDefinition#primary_key`
-
由 Ryuta Kamizono 提交于
Because call the `column` method and set the `options[:primary_key]` is handled at `super`, here need only treat the `options[:default]`.
-
由 Alex Robbin 提交于
-
由 Sean Griffin 提交于
Part of the larger refactoring to remove type casting from Arel. We can inform it that we already have the right type by wrapping the value in an `Arel::Nodes::Quoted`. This commit can be reverted when we have removed type casting from Arel in Rail 5.1
-
由 Sean Griffin 提交于
Part of the larger refactoring to remove type casting from Arel. We can inform it that we already have the right type by wrapping the value in an `Arel::Nodes::Quoted`. This commit can be reverted when we have removed type casting from Arel in Rail 5.1
-
由 Sean Griffin 提交于
Part of the larger refactoring to remove type casting from Arel. We can inform it that we already have the right type by wrapping the value in an `Arel::Nodes::Quoted`. This commit can be reverted when we have removed type casting from Arel in Rail 5.1
-
由 Sean Griffin 提交于
-
由 Sean Griffin 提交于
Part of a larger refactoring to remove type casting behavior from Arel
-
由 Sean Griffin 提交于
Part of the larger refactoring to remove type casting from Arel. We can inform it that we already have the right type by wrapping the value in an `Arel::Nodes::Quoted`. This commit can be reverted when we have removed type casting from Arel in Rail 5.1
-
由 Sean Griffin 提交于
Part of the larger refactoring to remove type casting from Arel. We can inform it that we already have the right type by wrapping the value in an `Arel::Nodes::Quoted`. This commit can be reverted when we have removed type casting from Arel in Rail 5.1
-
由 Sean Griffin 提交于
Part of the larger refactoring to remove type casting from Arel.
-
由 Sean Griffin 提交于
Part of the larger refactoring to remove type casting from Arel. We can inform it that we already have the right type by wrapping the value in an `Arel::Nodes::Quoted`. This commit can be reverted when we have removed type casting from Arel in Rail 5.1
-
由 Sean Griffin 提交于
Part of the larger refactoring to remove type casting from Arel. We can inform it that we already have the right type by wrapping the value in an `Arel::Nodes::Quoted`. This commit can be reverted when we have removed type casting from Arel in Rail 5.1
-
由 Sean Griffin 提交于
There are several valid cases where right now we can't determine the association's class in a call to `where`. In these cases, we can fall back to casting by looking up the column from the connection adapter (which is what happens right now when we fall through to Arel) This is ugly, and since we're trying to separate the concept of a type from a column, I'd like to remove it in the future. The problem basically comes down to this: Liquid.joins(molecules: :electrons) .where("molecules.name" => "something", "electrons.name" => "something") The hash in this case will turn into: { molecules: { name: "something" }, electrons: { name: "something" }, } What we actually need is: { molecules: { name: "something", electrons: { name: "something" }, } } /cc @mrgilman
-
由 Sean Griffin 提交于
This code could use some much heavier refactoring. It looks like `build_relation` duplicates most of the logic of `Relation#where` and `PredicateBuilder` with regards to handling associations and attribute aliases
-
由 Sean Griffin 提交于
Part of the larger refactoring to remove type casting from Arel. Since we've already cast the value a few lines above, we don't need to re-cast it later. We can inform Arel of this by wrapping it in an `Arel::Nodes::Quoted`, which will no longer be required in Rails 5.1
-
由 Sean Griffin 提交于
We will always have the correct type for this query, so no casting is needed. We inform Arel that we already have the right type by wrapping it in an `Arel::Nodes::Quoted` (which we will no longer need to do in Rails 5.1)
-
由 Sean Griffin 提交于
This will allow eager type casting to take place as needed. There doesn't seem to be any particular reason that the `in` statement was forced for single values, and the commit message where it was introduced gives no context. See https://github.com/rails/rails/commit/d90b4e2615e8048fdeffc6dffe3246704adee01f
-