- 25 3月, 2015 1 次提交
-
-
由 Lars Kanis 提交于
The type map was introduced in aafee233, but wasn't properly filled. This mainly adjusts many locations, that expected strings instead of integers or boolean. add_pg_decoders is moved after setup of the StatementPool, because execute_and_clear could potentially make use of it.
-
- 18 2月, 2015 1 次提交
-
-
由 Ryuta Kamizono 提交于
Lowercase raw SQL has been replaced by 07b659ca already. This commit replaces everything else of raw SQL.
-
- 03 2月, 2015 1 次提交
-
-
由 Vipul A M 提交于
-
- 28 1月, 2015 1 次提交
-
-
由 Sean Griffin 提交于
`bound_attributes` is now used universally across the board, removing the need for the conversion layer. These changes are mostly mechanical, with the exception of the log subscriber. Additional, we had to implement `hash` on the attribute objects, so they could be used as a key for query caching.
-
- 31 12月, 2014 1 次提交
-
-
由 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.
-
- 18 11月, 2014 2 次提交
-
-
由 Sean Griffin 提交于
Oh hey, we got to remove some code because of that!
-
由 Sean Griffin 提交于
Arel handles this for us automatically. Updated tests, as BindParam is no longer a subclass of SqlLiteral. We should remove the second argument to substitute_at entirely, as it's no longer used
-
- 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 1 次提交
-
-
由 Agis- 提交于
Fixes #16623 introduced by https://github.com/rails/rails/commit/3d5a2019bcccc6fb01bee4811ca669f4383edb51
-
- 30 5月, 2014 2 次提交
- 08 5月, 2014 1 次提交
-
-
由 Yves Senn 提交于
This test was inspired by #14866. That PR would break this functionality and we should make sure we notice that in the future.
-
- 11 4月, 2014 2 次提交
- 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.
-
- 13 2月, 2014 1 次提交
-
-
由 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.
-
- 29 12月, 2013 1 次提交
-
-
由 Kuldeep Aggarwal 提交于
-
- 23 12月, 2013 1 次提交
-
-
由 schneems 提交于
Currently if you attempt to use a database that does not exist you get an error: ``` PG::ConnectionBad FATAL: database "db_error" does not exist ``` The solution is easy, create and migrate your database however new developers may not know these commands by memory. Instead of requiring the developer to search for a solution, tell them how to fix the problem in the error message: ``` ActiveRecord::NoDatabase: FATAL: database "db_error" does not exist Run `$ bin/rake db:create db:migrate` to create your database ``` Active Record should not know about `rake db:migrate` so this additional information needs to come from the railtie. Potential alternative implementation suggestions are welcome.
-
- 19 12月, 2013 1 次提交
-
-
由 Kuldeep Aggarwal 提交于
Previously, executing an insert SQL in PostgreSQL with a command like this: insert into articles( number) values( 5152 ) would not work because the adapter was unable to extract the correct articles table name.
-
- 15 8月, 2013 1 次提交
-
-
由 Nikolay Kondratyev 提交于
-
- 03 7月, 2013 1 次提交
-
-
由 Francesco Rodriguez 提交于
-
- 13 5月, 2013 1 次提交
-
-
由 Rafael Mendonça França 提交于
Deprecate SchemaStatements#distinct, and make SchemaStatements#columns_for_distinct nodoc. Conflicts: activerecord/CHANGELOG.md
-
- 10 5月, 2013 1 次提交
-
-
由 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.
-
- 26 3月, 2013 1 次提交
-
-
由 Ranjay Krishna 提交于
Created a layer of abstraction for the valid type checking in schema dumper. Now, connection handles the check for valid types so that each database can handle the changes individually.
-
- 01 3月, 2013 1 次提交
-
-
由 kennyj 提交于
-
- 16 2月, 2013 1 次提交
-
-
由 Jon Leighton 提交于
This reverts commit c321b309. Conflicts: activerecord/lib/active_record/connection_adapters/abstract_mysql_adapter.rb activerecord/lib/active_record/connection_adapters/sqlite3_adapter.rb Reason: failing test 1) Error: test_valid_column(ActiveRecord::ConnectionAdapters::SQLite3AdapterTest): NoMethodError: undefined method `column' for test/cases/adapters/sqlite3/sqlite3_adapter_test.rb:29:in `test_valid_column'
-
- 12 2月, 2013 1 次提交
-
-
由 Ranjay Krishna 提交于
-
- 21 11月, 2012 1 次提交
-
-
由 Semyon Perepelitsa 提交于
-
- 05 10月, 2012 1 次提交
-
-
由 Yves Senn 提交于
-
- 08 4月, 2012 1 次提交
-
-
由 Doug Cole 提交于
-
- 02 4月, 2012 1 次提交
-
-
由 Doug Cole 提交于
-
- 01 4月, 2012 2 次提交
- 25 2月, 2012 1 次提交
-
-
由 kennyj 提交于
-
- 09 2月, 2012 1 次提交
-
-
由 Marcelo Silveira 提交于
-
- 11 6月, 2011 1 次提交
-
-
由 Paul Gallagher 提交于
* add/cleanup tests
-
- 10 6月, 2011 2 次提交
-
-
由 Paul Gallagher 提交于
* tidy test code and fix my typo
-
由 Paul Gallagher 提交于
* table_exists? scoped by schema search path unless schema is explicitly named. Added tests and doc to clarify the behaviour * extract_schema_and_table tests and implementation extended to cover all cases * primary_key does not ignore schema information * add current_schema and schema_exists? methods * more robust table referencing in insert_sql and sql_for_insert methods
-
- 07 6月, 2011 1 次提交
-
-
由 Aaron Patterson 提交于
-