- 03 4月, 2014 2 次提交
-
-
由 Dmitry Lavrov 提交于
-
由 Guo Xiang Tan 提交于
-
- 02 4月, 2014 4 次提交
-
-
由 Dave Lee 提交于
Expand the query used in #table_exists? to include materialized views in the kinds of relations it searches.
-
由 Yves Senn 提交于
Also do not use transactional fixtures. We drop the type and the table after every run, so there is nothing for the transaction to clean up.
-
由 Guo Xiang Tan 提交于
Creating and dropping similar tables within the same connection causes postgresql to look up old values in the cache of tables which have already been dropped.
-
- 01 4月, 2014 1 次提交
-
-
由 Yves Senn 提交于
I ran the whole test suite and compared the old to the new types. Following is the list of types that did change with this patch: ``` DIFFERENT TYPE FOR mood: NEW: enum, BEFORE: DIFFERENT TYPE FOR floatrange: NEW: floatrange, BEFORE: float ``` The `floatrange` is a custom type. The old type `float` was simply a coincidence form the name `floatrange` and our type-guessing.
-
- 31 3月, 2014 1 次提交
-
-
由 Luke Steensen 提交于
fixes #10613
-
- 29 3月, 2014 1 次提交
-
- 28 3月, 2014 3 次提交
- 27 3月, 2014 1 次提交
-
-
由 Yves Senn 提交于
This will keep the test suite passing with older PG installations.
-
- 21 3月, 2014 1 次提交
-
-
由 Guo Xiang Tan 提交于
This setups the helper method which other tests can benefit from.
-
- 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.
-
- 18 3月, 2014 1 次提交
-
-
由 Matthew Draper 提交于
It wasn't doing anything beyond clearing the statement cache.
-
- 15 3月, 2014 1 次提交
-
-
由 Guo Xiang Tan 提交于
Follow-Up to https://github.com/rails/rails/pull/14348 Ensure that SQLCounter.clear_log is called after each test. This is a step to prevent side effects when running tests. This will allow us to run them in random order.
-
- 11 3月, 2014 2 次提交
-
-
由 Yves Senn 提交于
-
由 lsylvester 提交于
citext makes it possible to use AR Hash finders for case-insensitive matching as sql UPPER/LOWER functions are not needed.
-
- 04 3月, 2014 3 次提交
- 03 3月, 2014 1 次提交
-
-
由 Vipul A M 提交于
- unused variable in PG Adapter. - Ambiguous argument warning from range_test for use - to + Infinity range without brackets.
-
- 26 2月, 2014 3 次提交
-
-
由 Yves Senn 提交于
-
由 Yves Senn 提交于
-
由 Yves Senn 提交于
This test currently outputs the following warning: ``` unknown OID: current_mood(3567879) (SELECT "postgresql_enums".* FROM "postgresql_enums" ORDER BY "postgresql_enums"."id" ASC LIMIT 1) unknown OID: current_mood(3567879) (SELECT "postgresql_enums".* FROM "postgresql_enums" WHERE "postgresql_enums"."id" = $1 LIMIT 1) ``` We have an open PR to deal with this issue. It will dynamically register the OID for enum columns. This test case is merely to exhibit the current behavior of PostgreSQL enum columns.
-
- 23 2月, 2014 2 次提交
-
-
由 Yves Senn 提交于
The Ruby Range object does not support excluding beginnings. We currently support excluding beginnings for some subtypes using manually by incrementing them (now using the `#succ` method). This is approach is flawed as it's not equal to an excluding beginning. This commit deprecates the current support for excluding beginnings. It also raises an `ArgumentError` for subtypes that do not implement the `succ` method. This is a temporary solution to get rid of the broken state. We might still add complete support for excluding beginnings afterwards. (Probably with a new `PGRange` object, which acts like a `Range` but has excluding beginnings.
-
由 Yves Senn 提交于
This gets AR working with custom defined range types. It also removes the need for subtype specific branches in `OID::Range`. This expands the interface of all `OID` types with the `infinity` method. It's responsible to provide a value for positive and negative infinity.
-
- 19 2月, 2014 1 次提交
-
-
由 Aaron Patterson 提交于
Thanks Godfrey Chan for reporting this! Fixes: CVE-2014-0080
-
- 17 2月, 2014 1 次提交
-
-
由 Josh Goodall 提交于
We didn't have enough encoding for the wire protocol to store an array of hstore types. So, further encode any hstore that is an array member. Whilst we're here, ensure it's an HashWithIndifferentAccess being returned, to be consistent with other serialized forms, and add testing for arrays of hstore. So now the following migration: enable_extension "hstore" create_table :servers do |t| t.string :name t.hstore :interfaces, array: true end produces a model that can used like this, to store an array of hashes: server = Server.create(name: "server01", interfaces: [ { name: "bge0", ipv4: "192.0.2.2", state: "up" }, { name: "de0", state: "disabled", by: "misha" }, { name: "fe0", state: "up" }, ]) More at http://inopinatus.org/2013/07/12/using-arrays-of-hstore-with-rails-4/
-
- 13 2月, 2014 2 次提交
-
-
由 Yves Senn 提交于
remove created state after test execution, not before the next test. This prevents the leak of the `ex` table outside of a single test.
-
由 Matthew Draper 提交于
This should make it harder to accidentally break this test.
-
- 11 2月, 2014 1 次提交
-
-
由 Yves Senn 提交于
-
- 08 2月, 2014 1 次提交
-
-
由 Andrew White 提交于
If the test is run in a timezone that is behind UTC it fails because the time generated is ahead of 0000-01-01 00:00:00. Just increase the time subtracted so that timezone has no effect.
-
- 01 2月, 2014 1 次提交
-
-
由 Mauricio Linhares 提交于
-
- 18 1月, 2014 1 次提交
-
-
由 Aaron Patterson 提交于
-
- 17 1月, 2014 1 次提交
-
-
由 Jonathan Baudanza 提交于
-
- 16 1月, 2014 1 次提交
-
-
由 Yves Senn 提交于
-
- 07 1月, 2014 1 次提交
-
-
由 Nishant Modak 提交于
- Earlier, change_table was creating database-agnostic object. - After this change, it will create correct object based on current database adapter. - This will ensure that create_table and change_table will get same objects. - This makes update_table_definition method public and nodoc. - Fixes #13577 and #13503
-
- 29 12月, 2013 1 次提交
-
-
由 Kuldeep Aggarwal 提交于
-