| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The bug is that an error would be raised while attempting to convert a
template from one encoding to another.
Please see http://redmine.ruby-lang.org/issues/5564 for more details.
The workaround is to load all conversions into memory ahead of time,
and will only happen if the ruby version is *exactly* 1.9.3p0. The
hope is obviously that the underlying problem will be resolved in
the next patchlevel release of 1.9.3.
|
| | |
| | |
| | |
| | | |
This reverts commit 10773f94eae0dacf10e2ed0c28f6bb73805c2521.
|
|\ \ \
| | | |
| | | | |
Refactored pluralize and singularize into a common method
|
| | | |
| | | |
| | | |
| | | | |
See diff discussion on rails/#3536.
|
|\ \ \ \
| | | | |
| | | | | |
Update ActiveRecord#attribute_present? to work as documented
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
"Returns true if the specified attribute has been set by the user or by
a database load and is neither nil nor empty?"
Fixes #1613
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is a first implementation, EXPLAIN is highly
dependent on the database and I have made some
compromises.
On one hand, the method allows you to run the most
common EXPLAIN and that's it. If you want EXPLAIN
ANALYZE in PostgreSQL you need to do it by hand.
On the other hand, I've tried to construct a string
as close as possible to the ones built by the
respective shells. The rationale is that IMO the
user should feel at home with the output and
recognize it at first sight. Per database.
I don't know whether this implementation is going
to work well. Let's see whether people like it.
|
|\ \ \ \
| | | | |
| | | | | |
Add arel to Gemfile on apps generated in edge Rails
|
|/ / / / |
|
| | | | |
|
| | | | |
|
|/ / /
| | |
| | |
| | | |
events while a block runs
|
| | | |
|
|\ \ \
| | | |
| | | | |
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
|