- 25 8月, 2014 1 次提交
-
-
由 Yves Senn 提交于
This is a reacon to https://github.com/rails/rails/commit/d6c1205584b1ba597db4071b168681678b1e9875#commitcomment-7502487 This backwards incompatibility was introduced with d6c12055 to fix #7516. However both `connection.default_sequence_name` and `model.sequence_name` are public API. The PostgreSQL adapter should honor the interface and return strings. /cc @matthewd @chancancode
-
- 24 8月, 2014 2 次提交
-
-
由 Godfrey Chan 提交于
* Require either FIRST or LAST qualifier for "NULLS ..." * Require whitespace before "NULLS ..."
-
由 Agis- 提交于
Fixes #16623 introduced by https://github.com/rails/rails/commit/3d5a2019bcccc6fb01bee4811ca669f4383edb51
-
- 24 7月, 2014 1 次提交
-
- 29 6月, 2014 1 次提交
-
-
由 Sean Griffin 提交于
The only case where we got a column that was not `nil`, but did not respond to `cast_type` was when type casting the default value during schema creation. We can look up the cast type, and add that object to the column definition. Will allow us to consistently rely on the type objects for type casting in all directions.
-
- 28 6月, 2014 1 次提交
-
-
由 Abdelkader Boudih 提交于
-
- 27 6月, 2014 8 次提交
- 30 5月, 2014 4 次提交
- 29 5月, 2014 1 次提交
-
-
由 Sean Griffin 提交于
- Create a consistent API across adapters for building new columns - Use it for custom properties so we don't get `UndefinedMethodError`s in stuff I'm implementing elsewhere.
-
- 27 5月, 2014 1 次提交
-
-
由 Kuldeep Aggarwal 提交于
-
- 24 5月, 2014 1 次提交
-
-
由 Sean Griffin 提交于
-
- 23 5月, 2014 1 次提交
-
-
由 Sean Griffin 提交于
Determining things like precision and scale in postgresql will require the given blocks to take additional arguments besides the OID. - Adds the ability to handle additional arguments to `TypeMap` - Passes the column type to blocks when looking up PG types
-
- 19 5月, 2014 1 次提交
-
- 15 5月, 2014 1 次提交
-
-
由 Rafael Mendonça França 提交于
-
- 14 5月, 2014 2 次提交
- 12 5月, 2014 2 次提交
-
-
由 Yves Senn 提交于
-
由 Patrick Robertson 提交于
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.
-
- 04 5月, 2014 1 次提交
-
-
由 Yves Senn 提交于
-
- 16 4月, 2014 1 次提交
-
-
由 Eric Chahin 提交于
Changed change_column in PG schema_statements.rb to make sure that the uuid_generate function was not being quoted.
-
- 11 4月, 2014 1 次提交
-
-
由 Yves Senn 提交于
[Yves Senn & Matthew Draper]
-
- 02 4月, 2014 1 次提交
-
-
由 Dave Lee 提交于
Expand the query used in #table_exists? to include materialized views in the kinds of relations it searches.
-
- 20 3月, 2014 1 次提交
-
-
由 Josh Williams 提交于
The pk_an_sequence_for query previously joined against pg_class's oid for rows in pg_depend, but pg_depend's objid may point to other system tables, such as pg_attrdef. If a row in one of those other tables coincidentally has the same oid as an (unrelated) sequence, that sequence name may be returned instead of the real one. This ensures that only the pg_depend entries pointing to pg_class are considered.
-
- 17 1月, 2014 1 次提交
-
-
由 Jonathan Baudanza 提交于
-
- 05 12月, 2013 1 次提交
-
-
由 Aaron Patterson 提交于
-
- 15 8月, 2013 1 次提交
-
-
由 Nikolay Kondratyev 提交于
-
- 16 7月, 2013 1 次提交
-
-
由 Yves Senn 提交于
-
- 26 6月, 2013 1 次提交
-
-
由 Andrey Deryabin 提交于
-
- 10 5月, 2013 2 次提交
-
-
由 Ben Woosley 提交于
Reject blank order_values within #columns_for_distinct, as the orders aren't used at all on non-postgres adapters.
-
由 Ben Woosley 提交于
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.
-