| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| | |
frodsan/remove_deprecated_clear_stale_cached_connections_method
Remove AR::Connection#clear_stale_cached_connections! deprecated method
|
| | |
|
|/ |
|
| |
|
|\
| |
| | |
Handle single quotes in PostgreSQL default column values
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
PostgreSQL escapes single quotes by using an additional single quote.
When Rails queries the column information, PostgreSQL returns the
default values with the escaped single quotes.
#extract_value_from_default now converts these to one single quote each.
Fixes #10881.
|
| | |
|
|\ \
| |/
|/|
| |
| | |
ranjaykrishna/push_add_column_options_to_schema_creation
Push add column options to schema creation
|
| |
| |
| |
| |
| |
| |
| |
| | |
removed two instances of add_column_options! from abstract_mysql_adapter
reworked rename_column_sql to remove add_column_options from schema_statements
changed to use new hash syntax.
|
| |
| |
| |
| |
| |
| | |
When then PostgreSQL visitor was [added](https://github.com/rails/rails/commit/6b7fdf3bf3675a14eae74acc5241089308153a34)
`add_column` was no longer receiving the column options directly. This
caused the options to be lost along the way.
|
| |
| |
| |
| |
| |
| | |
because this was deprecated.
Some testcases is failed, so I replaced nil to empty hash in add_reference.
|
|\ \
| | |
| | | |
Support array as root element in Postgresql JSON columns
|
| | | |
|
| | | |
|
|/ /
| |
| |
| | |
since 9.1.
|
| |
| |
| |
| |
| |
| | |
Deprecate SchemaStatements#distinct, and make SchemaStatements#columns_for_distinct nodoc.
Conflicts:
activerecord/CHANGELOG.md
|
| |
| |
| |
| | |
Don't modify args in TableDefinition#primary_key
|
| |
| |
| |
| | |
used at all on non-postgres adapters.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| |
| | |
patricksrobertson/bigserial_id_not_identifying_pk"
This reverts commit 3043d45eefc3776d5f3a9e7d212a01f99d869ef8, reversing
changes made to ca0275d36b395631725c4583db5a45c06443fdb9.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In #10410 it was noted that you can no longer create PK's with the
type of bigserial in PostgreSQL in 4.0.0.rc1. This is mostly
because the newer adapter is checking for column type with the
id column instead of just letting it pass through like it did
before.
Side effects:
You may just create a PK column of a type that you really don't
want to be your PK. As far as I can tell this was allowed in 3.2.X
and perhaps an exception should be raised if you try and do
something extremely dumb.
|
| | |
|
| | |
|
| |
| |
| |
| | |
It is new in PostgreSQL-9.2 .
|
| |
| |
| |
| | |
Introduced in 09ac1776abc0d3482f491f2d49f47bcb3d9a4ad7.
|
| |
| |
| |
| | |
without this, it's not possible to use UUID primary keys without uuid-ossp installed and activated
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
- 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.
|
| |
| |
| |
| |
| |
| |
| | |
This reverts commit 521035af530482d6d9ad2dae568eaeb0ab188e1c, reversing
changes made to 222011dbee842bbc60d3aaaa3145356b90a30fd1.
Reason: This broke the tests
|
|\ \
| | |
| | | |
DB with postgres string array column doesn't load fixtures well
|
| | | |
|
| | |
| | |
| | |
| | | |
bit column in Postgresql, because solving ambiguity.
|
| | | |
|
|/ / |
|
| | |
|
| |
| |
| |
| |
| |
| | |
as opposed to blank?
This is both faster and more correct, added tests to make sure this is not reverted again.
|
|\ \
| | |
| | | |
Make references with index:true pass Hash options to add_index
|
| | | |
|
|/ /
| |
| |
| | |
enum includes text or blob or ... hooked by wrong regex
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
once
This way the available options are only built for actually fetching the
algorithm in case the option is given.
The options are going to be necessary a second time only in case the option
is given but does not exist, which is supposed to be due to a typo or
something like that, so no problem.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
activerecord/lib/active_record/connection_adapters/abstract/schema_statements.rb
activerecord/test/cases/adapter_test.rb
guides/source/testing.md
[ci skip]
|