| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\ \
| | |
| | | |
Fixed an issue id false option is ignored on mysql/mysql2 (fix #3440)
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit 6aaae3de277b572f37e09f16ae12737c3c87dfb7, reversing
changes made to fdbc4e5f4e5746ebf558485348c841b33f038fda.
Reason: build failure.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This test is affected by a bug in Ruby 1.9.3p0 and trunk:
http://redmine.ruby-lang.org/issues/5564
Given we cannot fix it for ourselves, it is better to skip for now so
that we will easily see if further failures are introduced.
Jon Leighton is monitoring the bug report and will revert this when a
suitable solution is found (either a new Ruby release or a generic
workaround).
If you are using 1.9.3 in your app and have templates that are not in
UTF-8, you should add a workaround early on in the boot process. For
example, if your templates are Shift_JIS encoded, then add the
following in an initializer:
Encoding::Converter.new('Shift_JIS', 'UTF-8')
|
| | | |
|
| | | |
|
|\ \ \
| |_|/
|/| | |
Remove warnings by calling remove_method
|
| | | |
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This reverts commit d163d3bf7ebb98d90977974aed8f85b7ec678afd.
Reason: The alternate approach can be documented in the guide and
not disrupt the existing flow in the readme.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This reverts commit 36a5f48f9323c4a770c290a9a16ae58388e7925f.
Reason: Editing .gitignore in docrails is not allowed. Docrails is meant
only for documentation.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Defining after_initialize and after_find as ordinary methods like documented
in the guide doesn't work with Rails 3.1.1; now macro-style is used here, too.
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
This is in response to rails/rails#3504.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
subclasses
|
| | | | |
|
| | | | |
|
| | | | |
|
|\ \ \ \
| |_|_|/
|/| | | |
AR changes to support creating ordered (asc, desc) indexes
|
|/ / / |
|
| | | |
|
|\ \ \
| | | |
| | | | |
Fix test as one more has_many added
|
|/ / / |
|
|\ \ \
| | | |
| | | | |
Synchronize the gemspecs since CHANGELOG has been renamed to CHANGELOG.md
|
|/ / / |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Reasons:
* Markdown reads well as plain text, but can also be formatted.
* It will make it easier for people to read on the web as Github
formats the Markdown nicely.
* It will encourage a level of consistency when people are writing
CHANGELOG entries.
The script used to perform the conversion is at
https://gist.github.com/1339263
|
| | |
| | |
| | |
| | |
| | | |
This is to avoid confusing newbies, and to be consistent with the fact
that other options like :foreign_key already allow a symbol or a string.
|
|\ \ \
| | | |
| | | | |
Remove 'size' attribute from number_field form helper fixes #3454
|
| | | |
| | | |
| | | |
| | | |
| | | | |
f.number_field generates <input type="number", size="30"../> which is
invalid HTML5. See: http://dev.w3.org/html5/spec/Overview.html#number-state
|
|\ \ \ \
| |/ / /
|/| | | |
Sexier migrations
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Now you can omit |t| block parameter and all the t. from your migration code, that means, the syntax looks more Rails-3-ish, like the routes DSL and ActionMailer DSL.
Also, this change won't break any of your existing migration files, since the traditional syntax is still available.
|
| | | |
| | | |
| | | |
| | | | |
Preserve SELECT columns on the COUNT for finder_sql when possible
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
ActionView::Template, we get to see the actual underlying error rather than a NoMethodError.
This shows an encoding bug on Ruby 1.9.3.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Building the conditions of a nested through association could
potentially modify the conditions of the through and/or source
association.
This is a Bad Thing.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If a record is removed from a has_many :through, all of the join records
relating to that record should also be removed from the through
association's target.
(Previously the records were removed in the database, but only one was
removed from the in-memory target array.)
|
| | | |
| | | |
| | | |
| | | | |
Fixes #3425.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Fixes creating records in a through association with a polymorphic source
type.
|
|\ \ \ \
| | | | |
| | | | | |
treat USAGE as an ERB template
|