- 31 10月, 2018 1 次提交
-
-
由 Gannon McGibbon 提交于
[ci skip]
-
- 29 3月, 2018 1 次提交
-
-
由 Rafael França 提交于
Fix deprecation warnings from with_lock
-
- 24 10月, 2017 1 次提交
-
-
由 Rafael Mendonça França 提交于
-
- 22 8月, 2017 1 次提交
-
-
由 Yoshiyuki Hirano 提交于
-
- 30 7月, 2017 1 次提交
-
-
由 yuuji.yaginuma 提交于
It seems that it accepts only HTTPS connections. Ref: https://github.com/postgres/postgres/commit/7f77cbd996855a06fb742ea11adbe55c42b48fe2
-
- 20 7月, 2017 1 次提交
-
-
由 Kir Shatrov 提交于
-
- 02 7月, 2017 1 次提交
-
-
由 Matthew Draper 提交于
This reverts commit 3420a145, reversing changes made to afb66a5a.
-
- 01 7月, 2017 1 次提交
-
-
由 Kir Shatrov 提交于
-
- 07 2月, 2017 1 次提交
-
-
由 Marc Schütz 提交于
-
- 07 8月, 2016 1 次提交
-
-
由 Xavier Noria 提交于
-
- 10 9月, 2015 1 次提交
-
-
由 amitkumarsuroliya 提交于
Bumps from `5.6` to `5.7`
-
- 18 3月, 2015 1 次提交
-
-
由 Alexander Leishman 提交于
Update link in comments to point to latest MySQL production version documentation. See here for reference: http://dev.mysql.com/doc/refman/5.0/en/choosing-version.html
-
- 18 10月, 2013 1 次提交
-
-
由 sue445 提交于
Account.find(1, lock: true) -> DEPRECATION WARNING: Passing options to #find is deprecated. Please build a scope and then call #find on it.
-
- 31 5月, 2013 1 次提交
-
-
由 Pedro Fayolle 提交于
-
- 03 1月, 2013 1 次提交
-
-
由 Akira Matsuda 提交于
particularly, `all(options)` would warn
-
- 10 11月, 2012 1 次提交
-
-
由 AvnerCohen 提交于
-
- 19 1月, 2012 1 次提交
-
-
由 Olek Janiszewski 提交于
Add a `with_lock` method to ActiveRecord objects, which starts a transaction, locks the object (pessimistically) and yields to the block. The method takes one (optional) parameter and passes it to `lock!`. Before: class Order < ActiveRecord::Base def cancel! transaction do lock! # ... cancelling logic end end end After: class Order < ActiveRecord::Base def cancel! with_lock do # ... cancelling logic end end end
-
- 19 5月, 2011 1 次提交
-
-
由 John Paul Ashenfelter 提交于
Fixed what looks like minor cut/paste error in documentation for ActiveRecord::Locking:Pessimistic
-
- 18 5月, 2011 1 次提交
-
-
由 Sebastian Martinez 提交于
-
- 12 3月, 2011 1 次提交
-
-
由 Paco Guzman 提交于
-
- 15 2月, 2011 1 次提交
-
-
由 Sergii Boiko 提交于
Signed-off-by: NSantiago Pastorino <santiago@wyeworks.com>
-
- 09 11月, 2010 1 次提交
-
-
由 David Chelimsky 提交于
- persisted? is the API defined in ActiveModel - makes it easier for extension libraries to conform to ActiveModel APIs without concern for whether the extended object is specifically ActiveRecord [#5927 state:committed] Signed-off-by: NSantiago Pastorino <santiago@wyeworks.com>
-
- 01 9月, 2010 1 次提交
-
-
由 Emilio Tagua 提交于
-
- 12 9月, 2009 1 次提交
-
-
由 Shugo Maeda 提交于
-
- 02 5月, 2008 1 次提交
-
-
由 Xavier Noria 提交于
Signed-off-by: NPratik Naik <pratiknaik@gmail.com>
-
- 06 9月, 2006 2 次提交
-
-
由 David Heinemeier Hansson 提交于
Backed out of new_record? to new? transformation as it would screw up existing models that did boolean calls on "new" attributes [DHH] git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@5018 5ecf4fe2-1ee6-0310-87b1-e25e094e27de
-
由 David Heinemeier Hansson 提交于
Deprecated ActiveRecord::Base.new_record? in favor of ActiveRecord::Base.new? (old version still works until Rails 2.0) [DHH] git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@5017 5ecf4fe2-1ee6-0310-87b1-e25e094e27de
-
- 20 6月, 2006 1 次提交
-
-
由 Jeremy Kemper 提交于
Use the #lock method to obtain a row lock on a single record. Simply reloads the record with :lock => true. git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@4462 5ecf4fe2-1ee6-0310-87b1-e25e094e27de
-