s/ActiveRecord/Active Record according to api guidelines
This commit is contained in:
parent
9d15a35981
commit
087f8e16a6
|
@ -345,7 +345,7 @@ ActionController::Base.cache_store = MyCacheStore.new
|
|||
|
||||
h4. Cache Keys
|
||||
|
||||
The keys used in a cache can be any object that responds to either +:cache_key+ or to +:to_param+. You can implement the +:cache_key+ method on your classes if you need to generate custom keys. ActiveRecord will generate keys based on the class name and record id.
|
||||
The keys used in a cache can be any object that responds to either +:cache_key+ or to +:to_param+. You can implement the +:cache_key+ method on your classes if you need to generate custom keys. Active Record will generate keys based on the class name and record id.
|
||||
|
||||
You can use Hashes and Arrays of values as cache keys.
|
||||
|
||||
|
|
|
@ -216,19 +216,19 @@ h4. Configuring Active Record
|
|||
|
||||
* +config.active_record.pluralize_table_names+ specifies whether Rails will look for singular or plural table names in the database. If set to +true+ (the default), then the Customer class will use the +customers+ table. If set to +false+, then the Customers class will use the +customer+ table.
|
||||
|
||||
* +config.active_record.default_timezone+ determines whether to use +Time.local+ (if set to +:local+) or +Time.utc+ (if set to +:utc+) when pulling dates and times from the database. The default is +:utc+ for Rails, although ActiveRecord defaults to +:local+ when used outside of Rails.
|
||||
* +config.active_record.default_timezone+ determines whether to use +Time.local+ (if set to +:local+) or +Time.utc+ (if set to +:utc+) when pulling dates and times from the database. The default is +:utc+ for Rails, although Active Record defaults to +:local+ when used outside of Rails.
|
||||
|
||||
* +config.active_record.schema_format+ controls the format for dumping the database schema to a file. The options are +:ruby+ (the default) for a database-independent version that depends on migrations, or +:sql+ for a set of (potentially database-dependent) SQL statements.
|
||||
|
||||
* +config.active_record.timestamped_migrations+ controls whether migrations are numbered with serial integers or with timestamps. The default is +true+, to use timestamps, which are preferred if there are multiple developers working on the same application.
|
||||
|
||||
* +config.active_record.lock_optimistically+ controls whether ActiveRecord will use optimistic locking. By default this is +true+.
|
||||
* +config.active_record.lock_optimistically+ controls whether Active Record will use optimistic locking. By default this is +true+.
|
||||
|
||||
* +config.active_record.whitelist_attributes+ will create an empty whitelist of attributes available for mass-assignment security for all models in your app.
|
||||
|
||||
The MySQL adapter adds one additional configuration option:
|
||||
|
||||
* +ActiveRecord::ConnectionAdapters::MysqlAdapter.emulate_booleans+ controls whether ActiveRecord will consider all +tinyint(1)+ columns in a MySQL database to be booleans. By default this is +true+.
|
||||
* +ActiveRecord::ConnectionAdapters::MysqlAdapter.emulate_booleans+ controls whether Active Record will consider all +tinyint(1)+ columns in a MySQL database to be booleans. By default this is +true+.
|
||||
|
||||
The schema dumper adds one additional configuration option:
|
||||
|
||||
|
|
|
@ -809,7 +809,7 @@ That does not mean you're stuck with these limitations, though. The Ruby I18n ge
|
|||
I18n.backend = Globalize::Backend::Static.new
|
||||
</ruby>
|
||||
|
||||
You can also use the Chain backend to chain multiple backends together. This is useful when you want to use standard translations with a Simple backend but store custom application translations in a database or other backends. For example, you could use the ActiveRecord backend and fall back to the (default) Simple backend:
|
||||
You can also use the Chain backend to chain multiple backends together. This is useful when you want to use standard translations with a Simple backend but store custom application translations in a database or other backends. For example, you could use the Active Record backend and fall back to the (default) Simple backend:
|
||||
|
||||
<ruby>
|
||||
I18n.backend = I18n::Backend::Chain.new(I18n::Backend::ActiveRecord.new, I18n.backend)
|
||||
|
|
Loading…
Reference in New Issue