aboutsummaryrefslogtreecommitdiffstats
path: root/activerecord/lib/active_record/connection_adapters/postgresql
Commit message (Collapse)AuthorAgeFilesLines
* Use infinity constKonstantin Shabanov2013-08-221-2/+2
|
* Rescue invalid ip address exceptions on assign.Paul Nikitochkin2013-08-141-1/+5
| | | | In order that set attribute should not be bang method
* cast hstore values on write to be consistent with reading from the db.Yves Senn2013-08-081-4/+4
|
* Fix multidimensional PG arrays containing non-string itemsYves Senn2013-08-071-1/+9
|
* Refactor `ArrayParser`Vipul A M2013-07-261-15/+22
| | | | | * Constantize parse token * Remove extra param passed to `parse_data`
* `change_column` for PG adapter respects `:array` option.Yves Senn2013-07-161-2/+3
|
* remove deprecated `PostgreSQLAdapter#outside_transaction?` method.Yves Senn2013-07-031-7/+0
|
* Support array as root element in JSONAlexey Noskov2013-05-142-1/+3
|
* Reject blank order_values within #columns_for_distinct, as the orders aren't ↵Ben Woosley2013-05-101-1/+1
| | | | used at all on non-postgres adapters.
* Fix that #exists? can produce invalid SQL: "SELECT DISTINCT DISTINCT"Ben Woosley2013-05-101-7/+2
| | | | | | | | | | | | The combination of a :uniq => true association and the #distinct call in #construct_limited_ids_condition combine to create invalid SQL, because we're explicitly selecting DISTINCT, and also sending #distinct on to AREL, via the relation#distinct_value. Rather than build a select distinct clause in #construct_limited_ids_condition, I set #distinct! and pass just the columns into the select statement. This requires introducing a #columns_for_distinct method to return the select columns but not the statement itself.
* Make SchemaDumper emit "id: :uuid" when appropriate. Fixes #10451.Brian Buchanan2013-05-031-1/+2
|
* Fix loading of fixtures when the column type is a postgres array of strings.Chris Constantine2013-04-181-1/+1
| | | | - A string in an array of strings that has a quote char (') needs to have that quote char escaped if the array is getting wrapped in quote chars.
* Revert "Merge pull request #10043 from cconstantine/master"Rafael Mendonça França2013-04-181-15/+0
| | | | | | | This reverts commit 521035af530482d6d9ad2dae568eaeb0ab188e1c, reversing changes made to 222011dbee842bbc60d3aaaa3145356b90a30fd1. Reason: This broke the tests
* Merge pull request #10043 from cconstantine/masterRafael Mendonça França2013-04-181-0/+15
|\ | | | | DB with postgres string array column doesn't load fixtures well
| * Fix loading of string arrays in postgresChris Constantine2013-04-081-0/+15
| |
* | Fix #7619. 0x prefix must be added when assigning hexadecimal string into ↵kennyj2013-04-171-2/+4
| | | | | | | | bit column in Postgresql, because solving ambiguity.
* | Add OID::Bit for supporting bit string.kennyj2013-04-162-2/+19
| |
* | fix for the bytea/binary nil value bugMatt Aimonetti2013-04-141-0/+1
|/
* Do not calculate values if they are not going to be usedCarlos Antonio da Silva2013-03-301-7/+9
| | | | | | | | | When building the indexes list in PostgreSQL, IndexDefinition objects are only created if the query for the related attributes really returns something matching the attributes. In case it does not, the variables for building the definition objects were being created but not used.
* Add support for FULLTEXT and SPATIAL indexes using the :type flag for MySQL.Ken Mazaika2013-03-271-2/+2
|
* Adds support for concurrent indexing in PostgreSQL adapterDan McClain2013-03-251-6/+2
| | | | | | | | Adds support for algorithm option in MySQL indexes Moves USING and algorithm options upstream The syntax is still specific to the Adapter, so the actual executed string happens in the corresponding adapter
* Fix typoRafael Mendonça França2013-03-251-1/+1
|
* The sql_type method called here is fromRafael Mendonça França2013-03-251-6/+5
| | | | | | | ActiveRecord::ConnectionAdapters::Column See https://github.com/rails/rails/blob/28b8ca766e3e7c6c43d3ae900c99f8377153c62/activerecord/lib/active_record/connection_adapters/column.rb#L16
* Move away from column.sql_type in untested code tooMartin Schürrer2013-03-251-5/+6
|
* Make Postgres point type correspond to ruby array with two floats insideMartin Schürrer2013-03-253-5/+35
|
* Merge branch 'jlxw-patch-2'Rafael Mendonça França2013-03-231-2/+2
|\ | | | | | | Closes #9184
| * Fix regex to strip quotations from hstore valuesjlxw2013-03-231-2/+2
| | | | | | | | Previously regex did not strip quotation marks where hstore values were multi-line strings.
* | Custom index type support with :using.doabit2013-03-241-1/+11
|/
* add uuid primary key supportAaron Patterson2013-03-221-0/+9
|
* push the mysql add_column up to the abstract adapterAaron Patterson2013-03-221-10/+4
|
* allow multiple add columnsAaron Patterson2013-03-221-1/+1
|
* pull add_column_options! off the pg connection classAaron Patterson2013-03-221-0/+13
|
* add a pg visitor for dealing with schema modificationAaron Patterson2013-03-221-4/+21
|
* stop depending on sql_type in pgAaron Patterson2013-03-221-6/+8
|
* Cast number to string in PostgresŁukasz Strzałkowski2013-03-121-3/+6
| | | | fixes #9170
* Fix PostgreSQL TIMESTAMP WITH TIME ZONE to return ActiveSupport::TimeTroy Kruthoff2013-03-011-4/+1
| | | | | | | | | | In an AR model a timestamptz attribute would return a ruby string and AR tests did not check for any type casting. Previous tests would pass only because an assert_equal was being used on a Time.utc object, which will parse the right side of the eq to a valid Time instance for comparision. switch to test instance of Time instead of ActiveSupport::TimeWithZone
* also rename indexes when a table or column is renamedYves Senn2013-02-201-3/+6
| | | | When a table or a column is renamed related indexes kept their name. This will lead to confusing names. This patch renames related indexes when a column or a table is renamed. Only indexes with names generated by rails will be renamed. Indexes with custom names will not be renamed.
* Fix typoRafael Mendonça França2013-01-311-2/+2
|
* reloading type map on extension changingAaron Patterson2013-01-291-0/+4
|
* Fix cases where delete_records on a has_many association caused errorsDerek Kraan2013-01-271-0/+4
| | | | | | | | | | | | | because of an ambiguous column name. This happened if the association model had a default scope that referenced a third table, and the third table also referenced the original table (with an identical foreign_key). Mysql requires that ambiguous columns are deambiguated by using the full table.column syntax. Postgresql and Sqlite use a different syntax for updates altogether (and don't tolerate table.name syntax), so the fix requires always including the full table.column and discarding it later for Sqlite and Postgresql.
* Add postgresql range types supportbUg2013-01-234-59/+80
|
* Don't rely on Hash key's orderingVitor Baptista2013-01-161-2/+2
| | | | | | | | | | | | | | | | | | | If we set encoding latin1 for a PostgreSQL database, it calls PostgreSQLAdapter::create_database with options that have, among other things: { 'encoding' => 'latin1' } Then, we use reverse_merge(:encoding => "utf8") to setup the default encoding. In the end, the hash looks like: { :encoding => 'utf8', 'encoding' => 'latin1' } The call to options.symbolize_keys calls to_sym on each_key of this Hash. It usually means that the encoding passed overwrites the default utf8, but it's not guaranteed. So, we shouldn't rely on it. The same was happening in ActiveRecord::ConnectionHandling.
* These are already required through AS/railsAkira Matsuda2013-01-071-2/+0
| | | | | | * dependencies/autoload * concern * deprecation
* Support for PostgreSQL's ltree data type.Rob Worley2013-01-041-0/+1
|
* Reuse the Column integer converterRafael Mendonça França2013-01-031-1/+1
|
* #5523 Add ability for postgresql adapter to disable user triggers in ↵Gary S. Weaver2012-12-181-4/+12
| | | | disable_referential_integrity.
* AR supporting new int4range and int8range data type on PostgreSQL >= 9.2. ↵Alexey2012-12-171-4/+11
| | | | Fix realization
* AR supporting new intrange data type on PostgreSQL >= 9.2Alexey2012-12-164-0/+52
|
* Fix #8414. Performance problem with postgresql adapter primary_key function.kennyj2012-12-051-3/+2
|
* pg_namespace table isn't used.kennyj2012-12-051-1/+0
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-08 22:17:56 +0000