- 07 5月, 2016 1 次提交
-
-
由 Arthur Neves 提交于
-
- 06 5月, 2016 11 次提交
-
-
由 Arthur Neves 提交于
-
由 Arthur Neves 提交于
-
由 Arthur Neves 提交于
-
由 Arthur Neves 提交于
-
由 Arthur Neves 提交于
-
由 Arthur Neves 提交于
-
由 Arthur Neves 提交于
-
由 Arthur Neves 提交于
-
由 Arthur Neves 提交于
-
由 Arthur Neves 提交于
-
由 Arthur Neves 提交于
ConnectionHandler will not have any knowlodge of AR models now, it will only know about the specs. Like that we can decouple the two, and allow the same model to use more than one connection. Historically, folks used to create abstract AR classes on the fly in order to have multiple connections for the same model, and override the connection methods. With this, now we can override the `specificiation_id` method in the model, to return a key, that will be used to find the connection_pool from the handler.
-
- 05 5月, 2016 1 次提交
-
-
由 Joe Rafaniello 提交于
[ci skip]
-
- 04 5月, 2016 1 次提交
-
-
由 Vipul A M 提交于
Fix failing tests
-
- 03 5月, 2016 3 次提交
-
-
由 Erol Fornoles 提交于
-
由 yuuji.yaginuma 提交于
Follow up to 98264a13
-
由 Sean Griffin 提交于
Unlike `one?` and `none?`, `empty?` has interactions with methods outside of enumerable. It also doesn't fit in the same vein. `Topic.any?` makes sense. `Topic.empty?` does not, as `Topic` is not a container. Fixes #24808 Close #24812
-
- 02 5月, 2016 1 次提交
-
-
由 Ryuta Kamizono 提交于
`schema_creation` is not public API. https://github.com/rails/rails/blob/v5.0.0.beta4/activerecord/lib/active_record/connection_adapters/postgresql_adapter.rb#L121 https://github.com/rails/rails/blob/v5.0.0.beta4/activerecord/lib/active_record/connection_adapters/sqlite3_adapter.rb#L78
-
- 01 5月, 2016 1 次提交
-
-
由 Jon Moss 提交于
Rails should not be explicity mentioned within Active Record, since railties and the Rails ecosystem is not required for use.
-
- 30 4月, 2016 4 次提交
-
-
由 Vipul A M 提交于
Signed-off-by: NJeremy Daer <jeremydaer@gmail.com>
-
由 Ryuta Kamizono 提交于
Refactor of #22911. Signed-off-by: NJeremy Daer <jeremydaer@gmail.com>
-
由 Ryuta Kamizono 提交于
Follow up of 1683410c. Signed-off-by: NJeremy Daer <jeremydaer@gmail.com>
-
由 yui-knk 提交于
`ActiveRecord::Migration` needn't know about migration version compatibility lookup. Delegate it to the Compatibility module. Signed-off-by: NJeremy Daer <jeremydaer@gmail.com>
-
- 29 4月, 2016 3 次提交
-
-
由 Keenan Brock 提交于
-
由 Keenan Brock 提交于
Currently, loading the schema (schema_load) accesses the locking column (locking_column) which defaults the value (reset_locking_column) which invalidates the schema (reload_schema_from_cache) which forces another schema load. Good news: The second schema_load does accesses locking_column, but locking_column is set, so it does not reset_locking_column and it does not trigger an infinite loop. The solution is not invalidate the cache while default locking_column
-
由 Tom Kadwill 提交于
-
- 28 4月, 2016 1 次提交
-
-
由 eileencodes 提交于
-
- 26 4月, 2016 2 次提交
- 25 4月, 2016 4 次提交
-
-
由 Ryuta Kamizono 提交于
Example: create_table :users do |t| t.string :name t.index 'lower(name) varchar_pattern_ops' end Fixes #19090. Fixes #21765. Fixes #21819. Fixes #24359. Signed-off-by: NJeremy Daer <jeremydaer@gmail.com>
-
由 Seva Orlov 提交于
There is no need to fetch all table indexes in remove_index if name is specified. If name is wrong, then StatementInvalid will be raised. Signed-off-by: NJeremy Daer <jeremydaer@gmail.com>
-
由 Vipul A M 提交于
- Rename max to statement_limit - Remove magic number 1000 from everywhere - Defined StatementPool::DEFAULT_STATEMENT_LIMIT and started using it everywhere Signed-off-by: NJeremy Daer <jeremydaer@gmail.com>
-
由 Vipul A M 提交于
Adapters override `#supports_savepoints?` to return `true` if they support transaction savepoints. Defaults to `false`.
-
- 24 4月, 2016 7 次提交
-
-
由 Vipul A M 提交于
[ci skip]
-
由 Vipul A M 提交于
-
由 Ryuta Kamizono 提交于
-
由 Ryuta Kamizono 提交于
`IPAddr` is used in `OID::Cidr`.
-
由 Ryuta Kamizono 提交于
Follow up to #23458. Active Record supports MySQL >= 5.0 now.
-
由 Ryuta Kamizono 提交于
Follow up to #24685. `insert_versions_sql` is not public API.
-
由 Vipul A M 提交于
Make sure we handle explicitly passed nil's to lock_version as well. An explicitly passed nil value is now converted to 0 on LockingType, so that we don't end up with ActiveRecord::StaleObjectError in update record optimistic locking Fixes #24695
-