In Active Record, objects carry both persistent data and behavior which operates on that data.Active Record takes the opinion that ensuring data access logic as part of the object will educate users of that object on how to write to and read from the database.
Thus, explicit configuration would be needed only in those cases where you can't follow the standard convention.
By default, Active Record uses some naming conventions to find out how the mapping between models and database tables should be created.
Rails will pluralize your class names to find the respective database table.
Active Record gives us several mechanisms, the most important being the ability to: When writing applications using other programming languages or frameworks, it may be necessary to write a lot of configuration code.
This is particularly true for ORM frameworks in general.
However, if you follow the conventions adopted by Rails, you'll need to write very little configuration (in some cases no configuration at all) when creating Active Record models.The idea is that if you configure your applications in the very same way most of the time then this should be the default way.Active Record is the M in MVC - the model - which is the layer of the system responsible for representing business data and logic.Active Record facilitates the creation and use of business objects whose data requires persistent storage to a database.It is an implementation of the Active Record pattern which itself is a description of an Object Relational Mapping system.Active Record was described by Martin Fowler in his book .