- 18 4月, 2016 1 次提交
-
-
由 Vipul A M 提交于
-
- 17 4月, 2016 4 次提交
-
-
由 Jeremy Daer 提交于
Add support for specifying comments for tables, columns, and indexes in database itself
-
由 Jeremy Daer 提交于
don't remove `cable.js` when a channel is removed
-
由 Vipul A M 提交于
documentation for add_references index option [ci skip]
-
由 Alex Handley 提交于
- Add link for finding the addional options for index. - Add example for unique index as this is a common requirement. - Add link in guide for index options.
-
- 16 4月, 2016 6 次提交
-
-
由 Andrey Novikov 提交于
Comments are specified in migrations, stored in database itself (in its schema), and dumped into db/schema.rb file. This allows to generate good documentation and explain columns and tables' purpose to everyone from new developers to database administrators. For PostgreSQL and MySQL only. SQLite does not support comments at the moment. See docs for PostgreSQL: http://www.postgresql.org/docs/current/static/sql-comment.html See docs for MySQL: http://dev.mysql.com/doc/refman/5.7/en/create-table.html
-
由 yuuji.yaginuma 提交于
`cable.js` is required for other Channels.
-
由 Kasper Timm Hansen 提交于
Add TIP about app:update task in 'A Guide for Upgrading Ruby on Rails'
-
由 Jeremy Daer 提交于
Add changelog for #24542
-
由 Jeremy Daer 提交于
Fixed ActionCable::Connection::ClientSocketTest test
-
由 Javier Vidal 提交于
-
- 15 4月, 2016 11 次提交
-
-
由 Sean Griffin 提交于
Restore Hash#transform_keys behavior to always return a Hash instance
-
由 Sean Griffin 提交于
This brings the behavior more inline with other similar cases, such as receiving a hash when an array of scalars was expected. Prior to this commit, the key would be present, but the value would be `nil`
-
由 प्रथमेश Sonpatki 提交于
Fix broken link in 'Ruby on Rails 4.0 Release Notes'
-
由 Javier Vidal 提交于
-
由 Vipul A M 提交于
- Fixed ActionCable::Connection::ClientSocketTest that was overriding ActionCable::Connection::StreamTest test name - Only add attr_readers for required attributes
-
由 Vipul A M 提交于
update example to specify the Action Cable mount path [ci skip]
-
由 yuuji.yaginuma 提交于
Follow up to 8b69f1ee
-
由 Vipul A M 提交于
[ci skip]
-
由 Jeremy Daer 提交于
Should keep quoting behaivor of a time column value in sqlite3 adapter
-
由 Ryuta Kamizono 提交于
Follow up to #24542. In MySQL and PostgreSQL, a time column value is saved as ignored the date part of it. But in SQLite3, a time column value is saved as a string. We should keep previous quoting behavior in sqlite3 adapter. ``` sqlite> CREATE TABLE "foos" ("id" INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL, "start" time(0), "finish" time(4)); sqlite> INSERT INTO "foos" ("start", "finish") VALUES ('2000-01-01 12:30:00', '2000-01-01 12:30:00.999900'); sqlite> SELECT "foos".* FROM "foos"; 1|2000-01-01 12:30:00|2000-01-01 12:30:00.999900 sqlite> SELECT "foos".* FROM "foos" WHERE "foos"."start" = '2000-01-01 12:30:00' LIMIT 1; 1|2000-01-01 12:30:00|2000-01-01 12:30:00.999900 sqlite> SELECT "foos".* FROM "foos" WHERE "foos"."start" = '12:30:00' LIMIT 1; sqlite> ```
-
由 Sean Griffin 提交于
Run Action Cable callbacks through the worker pool
-
- 14 4月, 2016 18 次提交
-
-
由 Vipul A M 提交于
MariaDB documentation [ci skip]
-
由 iangilfillan 提交于
-
由 Jeremy Daer 提交于
Add `quoted_time` for truncating the date part of a time column value
-
由 Ryuta Kamizono 提交于
Context #24522. TIME column on MariaDB doesn't ignore the date part of the string when it coerces to time. ``` root@localhost [test] > CREATE TABLE `foos` (`id` int AUTO_INCREMENT PRIMARY KEY, `start` time(0), `finish` time(4)) ENGINE=InnoDB; Query OK, 0 rows affected (0.02 sec) root@localhost [test] > INSERT INTO `foos` (`start`, `finish`) VALUES ('2000-01-01 12:30:00', '2000-01-01 12:30:00.999900'); Query OK, 1 row affected, 2 warnings (0.00 sec) Note (Code 1265): Data truncated for column 'start' at row 1 Note (Code 1265): Data truncated for column 'finish' at row 1 root@localhost [test] > SELECT `foos`.* FROM `foos`; +----+----------+---------------+ | id | start | finish | +----+----------+---------------+ | 1 | 12:30:00 | 12:30:00.9999 | +----+----------+---------------+ 1 row in set (0.00 sec) root@localhost [test] > SELECT `foos`.* FROM `foos` WHERE `foos`.`start` = '2000-01-01 12:30:00' LIMIT 1; Empty set (0.00 sec) root@localhost [test] > SELECT `foos`.* FROM `foos` WHERE `foos`.`start` = '12:30:00' LIMIT 1; +----+----------+---------------+ | id | start | finish | +----+----------+---------------+ | 1 | 12:30:00 | 12:30:00.9999 | +----+----------+---------------+ 1 row in set (0.00 sec) ```
-
由 Jeremy Daer 提交于
Test against MariaDB 10.0
-
由 Richard Schneeman 提交于
[ci skip] Remove extra `so` from the Action Pack CHANGELOG
-
由 Prathamesh Sonpatki 提交于
-
由 Vipul A M 提交于
- Specify we want to run on latest stable ruby for mariadb - change in runs of builds Make mariadb? method publicly available
-
由 Sean Griffin 提交于
:nodoc: version method.
-
由 Vipul A M 提交于
Update ActionMailer base documentation [ci skip]
-
由 Tom Kadwill 提交于
-
由 Sean Griffin 提交于
Alternate implementation of #24162 with tests. The code had diverged too far on master to pull that implemenation directly. Fixes #23778 Close #24162 [Mattew Draper & Sean Griffin]
-
由 Sean Griffin 提交于
Fixed bug introduced in #24519. Makes build green again
-
由 Rafael França 提交于
Add ruby 2.2.2+ version requirement for Rails 5 apps
-
由 Bogdan Gusiev 提交于
-
由 Jeremy Daer 提交于
Switch to keyword args for attribute_changed?
-
由 Sean Griffin 提交于
Previously we were assuming that the only valid types for encoding were arrays and hashes. However, any JSON primitive is an accepted value by both PG and MySQL. This does involve a minor breaking change in the handling of `default` in the schema dumper. This is easily worked around, as passing a hash/array literal would have worked fine in previous versions of Rails. However, because of this, I will not be backporting this to 4.2 or earlier. Fixes #24234
-
由 Vipul A M 提交于
[ci skip]
-