./databases/ruby-activerecord70, Object-relational mapper framework (part of Rails 6.0)

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 7.0.1, Package name: ruby27-activerecord70-7.0.1, Maintainer: pkgsrc-users

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.0.


Master sites:

Filesize: 461 KB

Version history: (Expand)


CVS history: (Expand)


   2022-01-16 15:07:29 by Takahiro Kambe | Files touched by this commit (1) | Package updated
Log message:
databases/ruby-activerecord70: update to 7.0.1

7.0.1 (2021-01-06)

* Change QueryMethods#in_order_of to drop records not listed in values.

  in_order_of now filters down to the values provided, to match the
  behavior of the Enumerable version.

  Kevin Newton

* Allow named expression indexes to be revertible.

  Previously, the following code would raise an error in a reversible
  migration executed while rolling back, due to the index name not
  being used in the index removal.

	add_index(:settings, "(data->'property')", using: :gin, name: \ 
:index_settings_data_property)

  Fixes #43331.

  Oliver G√ľnther

* Better error messages when association name is invalid in the
  argument of ActiveRecord::QueryMethods::WhereChain#missing.

  ykpythemind

* Fix ordered migrations for single db in multi db environment.

  Himanshu

* Extract on update CURRENT_TIMESTAMP for mysql2 adapter.

  Kazuhiro Masuda

* Fix incorrect argument in PostgreSQL structure dump tasks.
  Updating the --no-comment argument added in Rails 7 to the correct
  --no-comments argument.

  Alex Dent

* Fix schema dumping column default SQL values for sqlite3.

  fatkodima

* Correctly parse complex check constraint expressions for PostgreSQL.

  fatkodima

* Fix timestamptz attributes on PostgreSQL handle blank inputs.

  Alex Ghiculescu

  Fix migration compatibility to create SQLite references/belongs_to
  column as integer when migration version is 6.0.

  Reference/belongs_to in migrations with version 6.0 were creating
  columns as bigint instead of integer for the SQLite Adapter.

  Marcelo Lauxen

* Fix joining through a polymorphic association.

  Alexandre Ruban

* Fix QueryMethods#in_order_of to handle empty order list.

  Post.in_order_of(:id, []).to_a Also more explicitly set the column
  as secondary order, so that any other value is still ordered.

  Jean Boussier

* Fix rails dbconsole for 3-tier config.

  Eileen M. Uchitelle

* Fix quoting of column aliases generated by calculation methods.

  Since the alias is derived from the table name, we can't assume the
  result is a valid identifier.

	class Test < ActiveRecord::Base
	  self.table_name = '1abc'
	end
	Test.group(:id).count
	# syntax error at or near "1" (ActiveRecord::StatementInvalid)
	# LINE 1: SELECT COUNT(*) AS count_all, "1abc"."id" AS \ 
1abc_id FROM "1...

  Jean Boussier
   2021-12-19 07:04:27 by Takahiro Kambe | Files touched by this commit (4)
Log message:
databases/ruby-activerecord70: add package version 7.0.0

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.0.