Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Followup of UUID default extension in the docs [ci skip] | Prathamesh Sonpatki | 2016-11-24 | 1 | -1/+1 |
| | | | | | | | - Mentioned clearly that for PostgreSQL < 9.4, you need to pass the default option with "uuid_generate_v4()" - Also updated PostgreSQL Active Record guide with this change. - https://github.com/rails/rails/pull/25395#r66877078 | ||||
* | Example had results the wrong way round [ci skip] | Patrick Copeland | 2016-06-16 | 1 | -2/+2 |
| | |||||
* | Use `add_index` instead of `execute` in guides [ci skip] | Ryuta Kamizono | 2016-05-28 | 1 | -1/+1 |
| | |||||
* | update supported version of PostgreSQL in docs [ci skip] | yuuji.yaginuma | 2016-02-03 | 1 | -1/+1 |
| | | | | Follow up to #23434 | ||||
* | Explain how HStore columns can be queried [ci skip] | Prathamesh Sonpatki | 2016-01-18 | 1 | -0/+4 |
| | | | | - Fixes #22876. | ||||
* | Introduce ApplicationRecord, an Active Record layer supertype | Genadi Samokovarov | 2015-12-16 | 1 | -15/+15 |
| | | | | | | | | | | | | | | | | It's pretty common for folks to monkey patch `ActiveRecord::Base` to work around an issue or introduce extra functionality. Instead of shoving even more stuff in `ActiveRecord::Base`, `ApplicationRecord` can hold all those custom work the apps may need. Now, we don't wanna encourage all of the application models to inherit from `ActiveRecord::Base`, but we can encourage all the models that do, to inherit from `ApplicationRecord`. Newly generated applications have `app/models/application_record.rb` present by default. The model generators are smart enough to recognize that newly generated models have to inherit from `ApplicationRecord`, but only if it's present. | ||||
* | Fix formatting of ActiveRecord PostgreSQL guide. | Christian Wesselhoeft | 2015-10-13 | 1 | -4/+6 |
| | |||||
* | Merge pull request #20981 from dkoprov/ar_postgres_enum_docs_addition | Sean Griffin | 2015-10-04 | 1 | -5/+41 |
|\ | | | | | Add more info on working with postgres ENUM type | ||||
| * | adds more info on working with postgres ENUM type | Dmitry Koprov | 2015-07-23 | 1 | -5/+41 |
| | | |||||
* | | use uuid method to define the UUID type [ci skip] | yuuji.yaginuma | 2015-08-08 | 1 | -1/+1 |
|/ | |||||
* | pg guide, explain the state of using UUID primary keys. Closes #20518. | Yves Senn | 2015-06-15 | 1 | -3/+9 |
| | | | | | | | [ci skip] The PostgreSQL 9.4 docs suggest to use `pgcrypto`. Howerver `create_table id: :uuid` will still default to `uuid_generate_v4()` | ||||
* | [ci skip] update ruby doc links; for rails next version ruby 2.2+ will be ↵ | Gaurav Sharma | 2015-05-20 | 1 | -2/+2 |
| | | | | supported only | ||||
* | Updated postgresql documentation link to use latest version [ci skip] | Ronak Jangir | 2015-05-20 | 1 | -19/+19 |
| | |||||
* | Merge pull request #19868 from createdbypete/guides-postgres-uuid-pgcrypto | Yves Senn | 2015-05-05 | 1 | -6/+9 |
|\ | | | | | | | | | | | Provide mention of pgcrypto extension for Postgres UUID support [ci skip] | ||||
| * | Provide mention of pgcrypto extension for uuids | Peter Rhoades | 2015-05-04 | 1 | -6/+9 |
|/ | | | | | | | | | From the Postgresql 9.4+ docs > If you only need randomly-generated (version 4) UUIDs, consider using the gen_random_uuid() function from the pgcrypto module instead. [ci skip] | ||||
* | Merge pull request #19806 from vircung/master | Yves Senn | 2015-04-18 | 1 | -0/+23 |
|\ | | | | | | | Improve documentation for uuid [ci skip] | ||||
| * | Improve documentation [ci skip] | Jacek Nakonieczny | 2015-04-18 | 1 | -0/+25 |
|/ | | | | Add information about usage `uuid` type with `reference` | ||||
* | - Changed `IN` to `ON` in markdown renderer condition | Vipul A M | 2015-01-14 | 1 | -1/+1 |
| | | | | - Changed `IN` to `ON` in all note sentences in guides. | ||||
* | warn about reading guides in GitHub | Xavier Noria | 2014-12-23 | 1 | -0/+2 |
| | | | | References #18148. | ||||
* | [ci skip] add `enable_extension` to PostgreSQL hstore example | yuuji.yaginuma | 2014-12-07 | 1 | -0/+3 |
| | |||||
* | [ci skip] correct example output and filename in pg guide | yuuji.yaginuma | 2014-11-22 | 1 | -2/+2 |
| | |||||
* | _will_change! method is not needed any more [ci skip] | Roberto Miranda | 2014-11-20 | 1 | -5/+0 |
| | | | ref #15674 | ||||
* | use correct operator in query based on JSON document | viditn91 | 2014-09-03 | 1 | -1/+2 |
| | |||||
* | pg guide, use the term `database views` to be specific. [ci skip] | Yves Senn | 2014-06-14 | 1 | -3/+3 |
| | |||||
* | pg guide, minor copy edits | Yves Senn | 2014-06-13 | 1 | -2/+4 |
| | |||||
* | pg guide, add index to PostgreSQL array example. [ci skip] | Yves Senn | 2014-06-09 | 1 | -1/+3 |
| | |||||
* | [ci skip] Make last note show up in postgresql guide. | Juanito Fatas | 2014-05-29 | 1 | -1/+1 |
| | |||||
* | pg guide, move introductory sentences into main content. [ci skip] | Yves Senn | 2014-05-19 | 1 | -7/+7 |
| | | | | This is a reaction to https://github.com/rails/rails/commit/7ca75f3789e316b6f3dc1f8000ec4f85c8ba32ea#commitcomment-6303828 | ||||
* | A tiny pass through the PostgreSQL guide [ci skip] | Robin Dupret | 2014-05-18 | 1 | -3/+4 |
| | |||||
* | typo: resulution -> resolution [ci skip] | Godfrey Chan | 2014-05-12 | 1 | -1/+1 |
| | |||||
* | pg guide, PostgreSQL legacy table view example. [ci skip] | Yves Senn | 2014-05-11 | 1 | -0/+59 |
| | |||||
* | pg guide, inet code example. [ci skip] | Yves Senn | 2014-05-08 | 1 | -3/+29 |
| | |||||
* | [ci skip] Add feature section and normalize prologue with other guides. | Juanito Fatas | 2014-05-07 | 1 | -3/+12 |
| | | | | | | Also change Json => JSON. Fill Ruby's Range & IPAddr link. | ||||
* | pg guides, some stylistic changes [ci skip] | Yves Senn | 2014-05-06 | 1 | -20/+21 |
| | |||||
* | pg guide, advanced features [ci skip] | Yves Senn | 2014-05-06 | 1 | -18/+46 |
| | |||||
* | pg guide, datatypes and examples. [ci skip] | Yves Senn | 2014-05-06 | 1 | -0/+309 |