- 31 12月, 2014 2 次提交
-
-
由 Rafael Mendonça França 提交于
-
由 Arthur Neves 提交于
When table has a composite primary key, the `primary_key` method for sqlite3 and postgresql was only returning the first field of the key. Ensures that it will return nil instead, as AR dont support composite pks.
-
- 28 12月, 2014 1 次提交
-
-
由 Ryuta Kamizono 提交于
-
- 19 12月, 2014 1 次提交
-
-
由 Yves Senn 提交于
-
- 28 11月, 2014 2 次提交
-
-
由 Ryuta Kamizono 提交于
-
由 Ryuta Kamizono 提交于
-
- 27 11月, 2014 1 次提交
-
-
由 Ryuta Kamizono 提交于
-
- 25 11月, 2014 2 次提交
-
-
由 Aaron Patterson 提交于
This allows us so abstract the migration from the type that is actually used by Rails. For example, ":string" may be a varchar or something, but the framework does that translation, and the app shouldn't need to know.
-
由 Aaron Patterson 提交于
-
- 23 11月, 2014 1 次提交
-
-
由 Sean Griffin 提交于
Also checked to make sure this does not affect foreign key constraints. (It doesn't). Fixes #12856 Closes #14088
-
- 21 11月, 2014 1 次提交
-
-
由 Aaron Patterson 提交于
-
- 01 11月, 2014 3 次提交
-
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Joe Rafaniello 提交于
Skip setting sequence on a table create if the value is 0 since it will start the first value at 1 anyway. This fixes the PG error 'setval: value 0 is out of bounds for sequence vms_id_seq...' encountered when migrating a new DB. BugzID: 15452,9772,13475,16850
-
- 18 9月, 2014 1 次提交
-
-
由 Geoff Harcourt 提交于
While investigating #16951 I found that another library's monkey-patching of `Enumerable` was causing the test migrations helper to break when trying to build the `CREATE DATABASE` statement. The prior approach used `#sum` to build the string from the options hash. As the code that combines the options to build the database statement is not user-facing, using `#inject` here instead will remove the only place where the database creation/migration code is dependent on ActiveSupport's monkey-patching of `Enumerable`.
-
- 17 9月, 2014 1 次提交
-
-
由 Yves Senn 提交于
Closes #16907. [Matthew Draper & Yves Senn]
-
- 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 提交于
-