Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
Commit | Credits | Log message |
7.1.5.1 25 Dec 2024 19:16:48
    |
Po-Chuan Hsieh (sunpoet)  |
databases/rubygem-activerecord71: Update to 7.1.5.1
Changes: https://github.com/rails/rails/releases |
7.1.5 21 Nov 2024 13:39:36
    |
Po-Chuan Hsieh (sunpoet)  |
databases/rubygem-activerecord71: Update to 7.1.5
Changes: https://github.com/rails/rails/releases |
7.1.4.2 26 Oct 2024 23:28:36
    |
Po-Chuan Hsieh (sunpoet)  |
databases/rubygem-activerecord71: Update to 7.1.4.2
Changes: https://github.com/rails/rails/releases |
7.1.4.1 22 Oct 2024 09:50:45
    |
Po-Chuan Hsieh (sunpoet)  |
databases/rubygem-activerecord71: Update to 7.1.4.1
Changes: https://github.com/rails/rails/releases |
7.1.4 18 Sep 2024 06:15:11
    |
Po-Chuan Hsieh (sunpoet)  |
databases/rubygem-activerecord71: Update to 7.1.4
Changes: https://github.com/rails/rails/releases |
7.1.3.4 06 Jun 2024 07:48:21
    |
Po-Chuan Hsieh (sunpoet)  |
databases/rubygem-activerecord71: Update to 7.1.3.4
Changes: https://github.com/rails/rails/releases |
7.1.3.3 19 May 2024 22:13:22
    |
Po-Chuan Hsieh (sunpoet)  |
databases/rubygem-activerecord71: Update to 7.1.3.3
Changes: https://github.com/rails/rails/releases |
7.1.3.2 09 Mar 2024 14:07:01
    |
Po-Chuan Hsieh (sunpoet)  |
databases/rubygem-activerecord71: Update to 7.1.3.2
Changes: https://github.com/rails/rails/releases |
7.1.3 21 Feb 2024 15:11:00
    |
Po-Chuan Hsieh (sunpoet)  |
databases/rubygem-activerecord71: Update to 7.1.3
Changes: https://github.com/rails/rails/releases |
7.1.2 14 Nov 2023 17:16:35
    |
Po-Chuan Hsieh (sunpoet)  |
databases/rubygem-activerecord71: Update to 7.1.2
Changes: https://github.com/rails/rails/releases |
7.1.1 01 Nov 2023 07:56:00
    |
Po-Chuan Hsieh (sunpoet)  |
databases/rubygem-activerecord71: Add rubygem-activerecord71 7.1.1
Active Record connects classes to relational database tables to establish an
almost zero-configuration persistence layer for applications. The library
provides a base class that, when subclassed, sets up a mapping between the new
class and an existing table in the database. In the context of an application,
these classes are commonly referred to as models. Models can also be connected
to other models; this is done by defining associations.
Active Record relies heavily on naming in that it uses class and association
names to establish mappings between respective database tables and foreign key
columns. Although these mappings can be defined explicitly, it's recommended to
follow naming conventions, especially when getting started with the library. |