aboutsummaryrefslogtreecommitdiffstats
path: root/guides/source/active_record_postgresql.md
Commit message (Collapse)AuthorAgeFilesLines
* Update links and code examples in the guides to use HTTPS where the host ↵Nathaniel Suchy2019-03-061-2/+2
| | | | supports it.
* Bump the minimum version of PostgreSQL to 9.3Yasuo Honda2018-11-251-1/+1
| | | | | | | | | | | | | | | | | | | | https://www.postgresql.org/support/versioning/ - 9.1 EOLed on September 2016. - 9.2 EOLed on September 2017. 9.3 is also not supported since Nov 8, 2018. https://www.postgresql.org/about/news/1905/ I think it may be a little bit early to drop PostgreSQL 9.3 yet. * Deprecated `supports_ranges?` since no other databases support range data type * Add `supports_materialized_views?` to abstract adapter Materialized views itself is supported by other databases, other connection adapters may support them * Remove `with_manual_interventions` It was only necessary for PostgreSQL 9.1 or earlier * Drop CI against PostgreSQL 9.2
* Merge pull request #33229 from ↵Matthew Draper2018-07-251-1/+1
|\ | | | | | | | | albertoalmagro/albertoalmagro/prefer-rails-command-over-bin-rails Prefer rails command over bin/rails
| * Recommend use of rails over bin/railsAlberto Almagro2018-07-061-1/+1
| | | | | | | | | | | | | | | | | | As discussed in #33203 rails command already looks for, and runs, bin/rails if it is present. We were mixing recommendations within guides and USAGE guidelines, in some files we recommended using rails, in others bin/rails and in some cases we even had both options mixed together.
* | Rails guides are now served over httpsPaul McMahon2018-07-241-1/+1
|/ | | | | http links will be redirected to the https version, but still better to just directly link to the https version.
* Active Record postgresql documentation for bit string types correctedSagar Kamble2018-05-061-1/+1
|
* Fix links in the psql guide [ci skip]Yauheni Dakuka2018-03-041-2/+2
|
* Change http postgresql.org links to https [ci skip]yuuji.yaginuma2017-07-301-22/+22
| | | | | It seems that it accepts only HTTPS connections. Ref: https://github.com/postgres/postgres/commit/7f77cbd996855a06fb742ea11adbe55c42b48fe2
* Document ActiveRecord's PostgreSQL-specific support for JSONB datatype in ↵Marc Rendl Ignacio2017-06-271-1/+6
| | | | | | RailsGuides [ci skip]
* [ci skip] Fix link in active_record_postgresql.mdYauheni Dakuka2017-06-091-1/+1
|
* Fix link in active_record_postgresql.mdYauheni Dakuka2017-06-091-1/+1
|
* Use proper output format [ci skip] (#27498)प्रथमेश Sonpatki2016-12-291-1/+1
|
* Followup of UUID default extension in the docs [ci skip]Prathamesh Sonpatki2016-11-241-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 Copeland2016-06-161-2/+2
|
* Use `add_index` instead of `execute` in guides [ci skip]Ryuta Kamizono2016-05-281-1/+1
|
* update supported version of PostgreSQL in docs [ci skip]yuuji.yaginuma2016-02-031-1/+1
| | | | Follow up to #23434
* Explain how HStore columns can be queried [ci skip]Prathamesh Sonpatki2016-01-181-0/+4
| | | | - Fixes #22876.
* Introduce ApplicationRecord, an Active Record layer supertypeGenadi Samokovarov2015-12-161-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 Wesselhoeft2015-10-131-4/+6
|
* Merge pull request #20981 from dkoprov/ar_postgres_enum_docs_additionSean Griffin2015-10-041-5/+41
|\ | | | | Add more info on working with postgres ENUM type
| * adds more info on working with postgres ENUM typeDmitry Koprov2015-07-231-5/+41
| |
* | use uuid method to define the UUID type [ci skip]yuuji.yaginuma2015-08-081-1/+1
|/
* pg guide, explain the state of using UUID primary keys. Closes #20518.Yves Senn2015-06-151-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 Sharma2015-05-201-2/+2
| | | | supported only
* Updated postgresql documentation link to use latest version [ci skip]Ronak Jangir2015-05-201-19/+19
|
* Merge pull request #19868 from createdbypete/guides-postgres-uuid-pgcryptoYves Senn2015-05-051-6/+9
|\ | | | | | | | | | | Provide mention of pgcrypto extension for Postgres UUID support [ci skip]
| * Provide mention of pgcrypto extension for uuidsPeter Rhoades2015-05-041-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/masterYves Senn2015-04-181-0/+23
|\ | | | | | | Improve documentation for uuid [ci skip]
| * Improve documentation [ci skip]Jacek Nakonieczny2015-04-181-0/+25
|/ | | | Add information about usage `uuid` type with `reference`
* - Changed `IN` to `ON` in markdown renderer conditionVipul A M2015-01-141-1/+1
| | | | - Changed `IN` to `ON` in all note sentences in guides.
* warn about reading guides in GitHubXavier Noria2014-12-231-0/+2
| | | | References #18148.
* [ci skip] add `enable_extension` to PostgreSQL hstore exampleyuuji.yaginuma2014-12-071-0/+3
|
* [ci skip] correct example output and filename in pg guideyuuji.yaginuma2014-11-221-2/+2
|
* _will_change! method is not needed any more [ci skip]Roberto Miranda2014-11-201-5/+0
| | | ref #15674
* use correct operator in query based on JSON documentviditn912014-09-031-1/+2
|
* pg guide, use the term `database views` to be specific. [ci skip]Yves Senn2014-06-141-3/+3
|
* pg guide, minor copy editsYves Senn2014-06-131-2/+4
|
* pg guide, add index to PostgreSQL array example. [ci skip]Yves Senn2014-06-091-1/+3
|
* [ci skip] Make last note show up in postgresql guide.Juanito Fatas2014-05-291-1/+1
|
* pg guide, move introductory sentences into main content. [ci skip]Yves Senn2014-05-191-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 Dupret2014-05-181-3/+4
|
* typo: resulution -> resolution [ci skip]Godfrey Chan2014-05-121-1/+1
|
* pg guide, PostgreSQL legacy table view example. [ci skip]Yves Senn2014-05-111-0/+59
|
* pg guide, inet code example. [ci skip]Yves Senn2014-05-081-3/+29
|
* [ci skip] Add feature section and normalize prologue with other guides.Juanito Fatas2014-05-071-3/+12
| | | | | | Also change Json => JSON. Fill Ruby's Range & IPAddr link.
* pg guides, some stylistic changes [ci skip]Yves Senn2014-05-061-20/+21
|
* pg guide, advanced features [ci skip]Yves Senn2014-05-061-18/+46
|
* pg guide, datatypes and examples. [ci skip]Yves Senn2014-05-061-0/+309
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-02 18:01:49 +0000