| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
order on the old ones
The previous behavior added a major backward incompatibility since it
impossible to have a upgrade path without major changes on the
application code.
We are taking the most conservative path to be consistent with the idea
of having a smoother upgrade on Rails 4.
We are reverting the behavior for what was in Rails 3.x and,
if needed, we will implement a new API to prepend the order clauses in
Rails 4.1.
|
| |
|
|\
| |
| | |
Update of 'The Asset Pipeline' guide for Rails 4.
|
| | |
|
|\ \
| | |
| | | |
Added Time#middle_of_day method
|
| | |
| | |
| | |
| | | |
Added middle_of_day method to Date and DateTime
|
|\ \ \
| | | |
| | | | |
Add installation instructions for FreeBSD [ci skip]
|
| | | |
| | | |
| | | |
| | | | |
Add packages required to setup the rails environment on FreeBSD.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
neerajdotname/log_should_mimick_original_log_method
interceptor should mimick original method
|
| | | | |
| | | | |
| | | | |
| | | | | |
This fix also makes the test order independent.
|
|\ \ \ \ \
| |_|/ / /
|/| | | | |
Fixing the broken URL [skip ci]
|
|/ / / / |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Use a lambda to ensure that the generated string respects the offset of
the time value. Also add DateTime#to_s(:iso8601) and Date#to_s(:iso8601)
for completeness.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
neerajdotname/use_method_with_active_record_default_timezone
use method with_active_record_default_timezone
|
| |/ / / |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Improved the doc about showing posts in getting started guide [ci skip]
|
| |/ / /
| | | |
| | | |
| | | | |
- Reference #11644
|
|\ \ \ \
| |/ / /
|/| | | |
remove duplicate method
|
|/ / /
| | |
| | |
| | | |
This method is already present in helper.rb
|
| | |
| | |
| | |
| | | |
for easy Javascript date parsing
|
|\ \ \
| | | |
| | | | |
grab executable from rubygems
|
| | | |
| | | |
| | | | |
As done here d7fc97d3f90c0e30865d32ce202658f03248cacc
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This reverts commit 10259c3e906da2191ef0d43cd664a3b5504d9f8c.
reason: this causes rake test_mysql and test_mysql2 fail
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Changed stylesheet load order in the stylesheet manifest generator.
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Cleanup of class_name
|
| |/ / / /
| | | | |
| | | | |
| | | | | |
Don't think class name is needed as by default belongs_to :select will be linked to Select class.
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
neerajdotname/fix_order_dependent_test_for_migration
fix order dependent test related to migration
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
If the order in which tests are executed is changed then test fails.
This commit ensures that all migrations are run before ensuring that
there are no pending migration.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
neerajdotname/make_test_order_independent_by_resetting_timezone
make test order independent by resetting timezone
|
| |/ / / / / |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
reset default timezone and make test order independent
|
| |/ / / / / |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
neerajdotname/make_order_independent_association_test
make test not depend on order
|
| |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
`NestedThroughAssociationsTest` adds records to `member_details` table.
When test performs `@member_details[0]` then the order of record
is not guaranteed. Hence it is best to start with a clean slate by
deleting unwanted records.
|
|\ \ \ \ \ \
| |_|/ / / /
|/| | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
To share a certain logic across other examples, let's add a sample SQL
code generated by the given Ruby code
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
sorry @robin850.
Thanks @fxn
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This reverts commit 700c6c65bcce17d4c61423ceaef031bcbe203337.
Bot the `sqlite3` and `sqlite3-ruby` gems exist.
https://rubygems.org/gems/sqlite3
https://rubygems.org/gems/sqlite3-ruby
In fact, they both point to the same github repository.
https://github.com/luislavena/sqlite3-ruby
However, the last one hasn't been released since 2011, while the first
one keeps getting regular releases.
|