- 18 1月, 2014 1 次提交
-
-
由 Aaron Patterson 提交于
-
- 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
-
- 24 12月, 2013 1 次提交
-
-
由 Carlos Antonio da Silva 提交于
The code uses these checks in several places to know what to do with a particular column, for instance AR attribute query methods has a branch like this: if column.number? !value.zero? end This should never be true for array columns, since it would be the same as running [].zero?, which results in a NoMethodError exception. Fixing this by ensuring that array columns in PostgreSQL never return true for number?/text? checks. Since most of the array support was based on the postgres_ext lib, it's worth noting it does the same thing for numeric array columns too: https://github.com/dockyard/postgres_ext/blob/v1.0.0/lib/postgres_ext/active_record/connection_adapters/postgres_adapter.rb#L72 This extended the same logic for text columns to ensure consistency.
-
- 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.
-
- 14 12月, 2013 1 次提交
-
-
由 Cody Cutrer 提交于
also override drop_table in AbstractMySQLAdapter to properly drop temporary tables without committing the transaction
-
- 06 12月, 2013 1 次提交
-
-
由 Aaron Patterson 提交于
-
- 05 12月, 2013 1 次提交
-
-
由 Aaron Patterson 提交于
-
- 12 11月, 2013 1 次提交
-
-
由 Ben Woosley 提交于
Drop some comments that document the implementation rather than the interface.
-
- 10 11月, 2013 1 次提交
-
-
由 Rafael Mendonça França 提交于
-
- 09 11月, 2013 1 次提交
-
-
由 Yves Senn 提交于
The log output used to be confusing in situation where type casting has "unexpected" effects. For example when finding records with a `String`. BEFORE: irb(main):002:0> Event.find("im-no-integer") D, [2013-11-09T11:10:28.998857 #1706] DEBUG -- : Event Load (4.5ms) SELECT "events".* FROM "events" WHERE "events"."id" = $1 LIMIT 1 [["id", "im-no-integer"]] AFTER: irb(main):002:0> Event.find("im-no-integer") D, [2013-11-09T11:10:28.998857 #1706] DEBUG -- : Event Load (4.5ms) SELECT "events".* FROM "events" WHERE "events"."id" = $1 LIMIT 1 [["id", 0]]
-
- 25 10月, 2013 1 次提交
-
- 22 10月, 2013 1 次提交
-
-
由 Rafael Mendonça França 提交于
This is causing every default value in PostreSQL database to being handled as default function. Fixes #12581
-
- 14 10月, 2013 2 次提交
-
-
由 Rafael Mendonça França 提交于
-
由 Rafael Mendonça França 提交于
-
- 05 10月, 2013 4 次提交
-
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
This is to be consistent with the way the mysql2 adapter times queries
-
- 30 9月, 2013 1 次提交
-
-
由 Yves Senn 提交于
-
- 12 9月, 2013 1 次提交
-
-
由 Rafael Mendonça França 提交于
When the adapter is with prepared statement disabled and the binds array is not empty the connection adapter will try to set the binds values and will fail. Now we are checking if the adapter has the prepared statement disabled. Fixes #12023
-
- 08 8月, 2013 1 次提交
-
-
由 Yves Senn 提交于
-
- 02 8月, 2013 1 次提交
-
-
由 Paul Nikitochkin 提交于
Closes: #11706
-
- 10 7月, 2013 1 次提交
-
-
由 kennyj 提交于
-
- 20 6月, 2013 1 次提交
-
-
由 Dylan Markow 提交于
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.
-
- 15 5月, 2013 1 次提交
-
-
由 kennyj 提交于
-
- 08 5月, 2013 1 次提交
-
-
由 Aaron Patterson 提交于
This reverts commit 3043d45e, reversing changes made to ca0275d3.
-
- 07 5月, 2013 1 次提交
-
-
由 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.
-
- 05 5月, 2013 1 次提交
-
-
由 Akshay Khole 提交于
-
- 03 5月, 2013 1 次提交
-
-
由 Lars Kanis 提交于
It is new in PostgreSQL-9.2 .
-
- 02 5月, 2013 2 次提交
-
-
由 Carlos Antonio da Silva 提交于
Introduced in 09ac1776.
-
由 Chad Moone 提交于
without this, it's not possible to use UUID primary keys without uuid-ossp installed and activated
-
- 05 4月, 2013 1 次提交
-
-
由 Erik Peterson 提交于
-
- 26 3月, 2013 3 次提交
-
-
由 Dan McClain 提交于
Adds support for algorithm option in MySQL indexes Moves USING and algorithm options upstream The syntax is still specific to the Adapter, so the actual executed string happens in the corresponding adapter
-
由 Martin Schürrer 提交于
-
由 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.
-
- 23 3月, 2013 4 次提交
-
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-