Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | psql implementation of #index_name_exists? | Jonathan Baudanza | 2014-01-16 | 1 | -0/+13 |
| | |||||
* | make the type_map per connection. fixes #13182 | Aaron Patterson | 2013-12-04 | 1 | -1/+1 |
| | |||||
* | Merge pull request #10664 from aderyabin/docpatch | Yves Senn | 2013-10-29 | 1 | -1/+1 |
|\ | | | | | Fix doc in Postgres database creation [ci skip] | ||||
| * | Fix doc in Postgres database creation | Andrey Deryabin | 2013-06-25 | 1 | -1/+1 |
| | | |||||
* | | `change_column` for PG adapter respects `:array` option. | Yves Senn | 2013-07-16 | 1 | -2/+3 |
|/ | |||||
* | Reject blank order_values within #columns_for_distinct, as the orders aren't ↵ | Ben Woosley | 2013-05-10 | 1 | -1/+1 |
| | | | | used at all on non-postgres adapters. | ||||
* | Fix that #exists? can produce invalid SQL: "SELECT DISTINCT DISTINCT" | Ben Woosley | 2013-05-10 | 1 | -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 Buchanan | 2013-05-03 | 1 | -1/+2 |
| | |||||
* | Do not calculate values if they are not going to be used | Carlos Antonio da Silva | 2013-03-30 | 1 | -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 Mazaika | 2013-03-27 | 1 | -2/+2 |
| | |||||
* | Adds support for concurrent indexing in PostgreSQL adapter | Dan McClain | 2013-03-25 | 1 | -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 | ||||
* | Custom index type support with :using. | doabit | 2013-03-24 | 1 | -1/+11 |
| | |||||
* | add uuid primary key support | Aaron Patterson | 2013-03-22 | 1 | -0/+9 |
| | |||||
* | push the mysql add_column up to the abstract adapter | Aaron Patterson | 2013-03-22 | 1 | -10/+4 |
| | |||||
* | allow multiple add columns | Aaron Patterson | 2013-03-22 | 1 | -1/+1 |
| | |||||
* | pull add_column_options! off the pg connection class | Aaron Patterson | 2013-03-22 | 1 | -0/+13 |
| | |||||
* | add a pg visitor for dealing with schema modification | Aaron Patterson | 2013-03-22 | 1 | -4/+21 |
| | |||||
* | also rename indexes when a table or column is renamed | Yves Senn | 2013-02-20 | 1 | -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. | ||||
* | Add postgresql range types support | bUg | 2013-01-23 | 1 | -8/+0 |
| | |||||
* | Don't rely on Hash key's ordering | Vitor Baptista | 2013-01-16 | 1 | -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. | ||||
* | AR supporting new intrange data type on PostgreSQL >= 9.2 | Alexey | 2012-12-16 | 1 | -0/+8 |
| | |||||
* | Fix #8414. Performance problem with postgresql adapter primary_key function. | kennyj | 2012-12-05 | 1 | -3/+2 |
| | |||||
* | pg_namespace table isn't used. | kennyj | 2012-12-05 | 1 | -1/+0 |
| | |||||
* | Refactoring, testing and documenting pg_connection.distinct | Semyon Perepelitsa | 2012-11-21 | 1 | -13/+10 |
| | |||||
* | Postgresql doesn't accepts limits on text columns. | Victor Costan | 2012-11-20 | 1 | -0/+7 |
| | |||||
* | Migration of docs to 1.9 hash syntax | AvnerCohen | 2012-10-23 | 1 | -1/+1 |
| | |||||
* | #7914 Remove code for unsupported postgreSQL version. | Arturo Pie | 2012-10-13 | 1 | -3/+0 |
| | | | | | | | Remove parsing of character type default values for 8.1 formatting since Rails doesn't support postgreSQL 8.1 anymore. Remove misleading comment unrelated to code. | ||||
* | #7914 Using a better way to get the defaults from db. | Arturo Pie | 2012-10-13 | 1 | -5/+5 |
| | | | | | | | | | According to postgreSQL documentation: (http://www.postgresql.org/docs/8.2/static/catalog-pg-attrdef.html) we should not be using 'adsrc' field because this field is unaware of outside changes that could affect the way that default values are represented. Thus, I changed the queries to use "pg_get_expr(adbin, adrelid)" instead of the historical "adsrc" field. | ||||
* | PostgreSQL, quote table names when fetching the primary key. Closes #5920 | Yves Senn | 2012-10-05 | 1 | -1/+1 |
| | |||||
* | Query for sequence info also should be markd as SCHEMA. | kennyj | 2012-09-15 | 1 | -3/+3 |
| | |||||
* | Query for loading index info should be marked as SCHEMA. | kennyj | 2012-09-15 | 1 | -1/+1 |
| | |||||
* | Modularize postgresql adapter | Konstantin Shabanov | 2012-09-05 | 1 | -0/+446 |