| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\ \ \
| | | |
| | | | |
Use template0 option for creating activerecord test databases in build_database task with postgres
|
| | | |
| | | |
| | | |
| | | | |
build_database task
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
65843e1acc0c8d285ff79f8c9c49d4d1215440be
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
i.e. Oracle database does not support these isolation levels.
`:read_uncommitted` `:repeatable_read`
This commit also works with other databases which do not support
these isolation levels.
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Fix collisions with before and after validation callbacks.
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This commit allows a user to do something like:
before_validation :do_stuff, :on => [ :create, :update ]
after_validation :do_more, :on => [ :create, :update ]
|
|/ / / / |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Related to 761bc751d31c22e2c2fdae2b4cdd435b68b6d783 and
eb876c4d07130f15be2cac7be968cc393f959c62
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This reverts commit 761bc751d31c22e2c2fdae2b4cdd435b68b6d783.
This commit wasn't fixing any issue just using the same table for
different models with different primary keys.
|
| | | | |
|
| |/ /
|/| | |
|
| | |
| | |
| | |
| | | |
set utf8_unicode_ci collation on latin1 table.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
actionmailer/lib/action_mailer/base.rb
activesupport/lib/active_support/configurable.rb
activesupport/lib/active_support/core_ext/module/deprecation.rb
guides/source/action_controller_overview.md
guides/source/active_support_core_extensions.md
guides/source/ajax_on_rails.textile
guides/source/association_basics.textile
guides/source/upgrading_ruby_on_rails.md
While resolving conflicts, I have chosen to ignore changes done in
docrails at some places - these will be most likely 1.9 hash syntax
changes.
|
| | | |
| | | |
| | | |
| | | | |
Callbacks may interfere with each other.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
Fixes #3458.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
It's too hard to test this properly, so let's just check that there are
no errors.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If your database supports setting the isolation level for a transaction,
you can set it like so:
Post.transaction(isolation: :serializable) do
# ...
end
Valid isolation levels are:
* `:read_uncommitted`
* `:read_committed`
* `:repeatable_read`
* `:serializable`
You should consult the documentation for your database to understand the
semantics of these different levels:
* http://www.postgresql.org/docs/9.1/static/transaction-iso.html
* https://dev.mysql.com/doc/refman/5.0/en/set-transaction.html
An `ActiveRecord::TransactionIsolationError` will be raised if:
* The adapter does not support setting the isolation level
* You are joining an existing open transaction
* You are creating a nested (savepoint) transaction
The mysql, mysql2 and postgresql adapters support setting the
transaction isolation level. However, support is disabled for mysql
versions below 5, because they are affected by a bug
(http://bugs.mysql.com/bug.php?id=39170) which means the isolation level
gets persisted outside the transaction.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
jcoleman/should-unset-association-when-an-existing-record-is-destroyed
Unset association when existing record is destroyed.
|
| | | | |
| | | | |
| | | | |
| | | | | |
To avoid foreign key errors (and invalid data) in the database, when a belongs_to association is destroyed, it should also be nil'd out on the parent object.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Freeze columns before using them as hash keys
|
| | | | | |
| | | | | |
| | | | | | |
This reduces the number of allocated strings from columns * (rows + 1) to just columns.
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
AR::Base#attributes= is just an alias for AR::Base#assign_attributes
|
| | | | | | | |
|
| | | | | | | |
|
| |_|_|_|_|/
|/| | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
db:structure:load
"
Breaks db:setup because it tries to load the environment before creating the database.
This reverts commit 5ca11fefce6d83f5db399aa4412f1f1a0d42b2e6.
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Closes #6960
|
|/ / / / /
| | | | |
| | | | |
| | | | | |
reference to mass_assignment options
|
| | | | |
| | | | |
| | | | |
| | | | | |
references to mass assignment options
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Integrate strong_parameters in Rails 4
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
or new protection model
|
| | | | | | |
|