Path to this page:
./
databases/ruby-activerecord71,
Object-relational mapper framework (part of Rails 7.1)
Branch: CURRENT,
Version: 7.1.4.2,
Package name: ruby32-activerecord71-7.1.4.2,
Maintainer: pkgsrc-usersActive Record -- Object-relational mapping in Rails
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.
This is for Ruby on Rails 7.1.
Master sites:
Filesize: 535 KB
Version history: (Expand)
- (2024-10-27) Updated to version: ruby32-activerecord71-7.1.4.2
- (2024-10-21) Updated to version: ruby32-activerecord71-7.1.4.1
- (2024-09-22) Updated to version: ruby32-activerecord71-7.1.4
- (2024-06-05) Updated to version: ruby32-activerecord71-7.1.3.4
- (2024-05-22) Updated to version: ruby32-activerecord71-7.1.3.3
- (2024-02-24) Updated to version: ruby32-activerecord71-7.1.3.2
CVS history: (Expand)
2024-02-24 15:55:27 by Takahiro Kambe | Files touched by this commit (15) | |
Log message:
www/ruby-rails71: update to 7.1.3.2
Update Ruby on Rails 7.1 and related pacakges to 7.1.3.2
This includes security fix:
CVE-2024-26142 for www/ruby-actionpack71
CVE-2024-26143 for www/ruby-actionpack71
Action Pack
* Fix possible XSS vulnerability with the translate method in controllers
CVE-2024-26143
* Fix ReDoS in Accept header parsing
CVE-2024-26142
|
2024-02-04 16:14:03 by Takahiro Kambe | Files touched by this commit (1) | |
Log message:
databases/ruby-activerecord71: update to 7.1.3
Active Record (2024-01-16)
* Fix Migrations with versions older than 7.1 validating options given to
add_reference. [Hartley McGuire]
* Ensure reload sets correct owner for each association. [Dmytro Savochkin]
* Fix view runtime for controllers with async queries. [fatkodima]
* Fix load_async to work with query cache. [fatkodima]
* Fix polymorphic belongs_to to correctly use parent's
query_constraints. [fatkodima]
* Fix Preloader to not generate a query for already loaded association with
query_constraints. [fatkodima]
* Fix multi-database polymorphic preloading with equivalent table names.
When preloading polymorphic associations, if two models pointed to two
tables with the same name but located in different databases, the
preloader would only load one. [Ari Summer]
* Fix encrypted_attribute? to take into account context properties passed to
encrypts. [Maxime Réty]
* Fix find_by to work correctly in presence of composite primary keys.
[fatkodima]
* Fix async queries sometimes returning a raw result if they hit the query
cache.
ShipPart.async_count could return a raw integer rather than a Promise if
it found the result in the query cache. [fatkodima]
* Fix Relation#transaction to not apply a default scope.
The method was incorrectly setting a default scope around its block:
Post.where(published: true).transaction do
Post.count # SELECT COUNT(*) FROM posts WHERE published = FALSE;
end
[Jean Boussier]
* Fix calling async_pluck on a none relation.
Model.none.async_pluck(:id) was returning a naked value instead of a
promise. [Jean Boussier]
* Fix calling load_async on a none relation.
Model.none.load_async was returning a broken result. [Lucas Mazza]
* TrilogyAdapter: ignore host if socket parameter is set.
This allows to configure a connection on a UNIX socket via DATABASE_URL:
DATABASE_URL=trilogy://does-not-matter/my_db_production?socket=/var/run/mysql.sock
[Jean Boussier]
* Fix has_secure_token calls the setter method on initialize. [Abeid Ahmed]
* Allow using object_id as a database column name.
It was available before rails 7.1 and may be used as a part of polymorphic
relationship to object where object can be any other database record.
[Mikhail Doronin]
* Fix rails db:create:all to not touch databases before they are created.
[fatkodima]
|
2023-11-30 16:24:18 by Takahiro Kambe | Files touched by this commit (5) |
Log message:
databases/ruby-activerecord71: add version 7.1.2
Active Record -- Object-relational mapping in Rails
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.
This is for Ruby on Rails 7.1.
|