- 15 10月, 2012 19 次提交
-
-
由 Joshua Peek 提交于
-
由 Joshua Peek 提交于
Conflicts: railties/test/application/configuration_test.rb
-
由 Joshua Peek 提交于
-
由 Joshua Peek 提交于
-
由 Joshua Peek 提交于
-
由 Joshua Peek 提交于
-
由 Jeremy Kemper 提交于
-
由 Santiago Pastorino 提交于
Removed useless "extend SanitizeHelper::ClassMethods"
-
由 Santiago Pastorino 提交于
Minor cleanup, helper method was only used once
-
由 Andrey Samsonov 提交于
Since SanitizeHelper includes ActiveSupport::Concern, extending of it ClassMethods is no needed.
-
由 Ayrton De Craene 提交于
-
由 Rafael Mendonça França 提交于
refactoring of uniqueness validate_each
-
由 Angelo Capilleri 提交于
get scope_value only one time dependig on reflection
-
由 Rafael Mendonça França 提交于
Fix typo in inet and cidr saving
-
由 Miguel Herranz 提交于
-
由 Jeremy Kemper 提交于
-
由 Jeremy Kemper 提交于
-
由 Jeremy Kemper 提交于
Use 1.9 Hash syntax in railties
-
由 Robin Dupret 提交于
-
- 14 10月, 2012 10 次提交
-
-
由 Jeremy Kemper 提交于
remove 'then' from conditional statement
-
由 Nihad Abbasov 提交于
-
由 Rafael Mendonça França 提交于
Fixes #7914 - PostgreSQL adapter doesn't fetch column defaults when using multiple schemas and domains
-
由 Arturo Pie 提交于
Remove parsing of character type default values for 8.1 formatting since Rails doesn't support postgreSQL 8.1 anymore. Remove misleading comment unrelated to code.
-
由 Arturo Pie 提交于
According to postgreSQL documentation: (http://www.postgresql.org/docs/8.2/static/catalog-pg-attrdef.html) we should not be using 'adsrc' field because this field is unaware of outside changes that could affect the way that default values are represented. Thus, I changed the queries to use "pg_get_expr(adbin, adrelid)" instead of the historical "adsrc" field.
-
由 Arturo Pie 提交于
-
由 Arturo Pie 提交于
PostgreSQL adapter properly parses default values when using multiple schemas and domains. When using domains across schemas, PostgresSQL prefixes the type of the default value with the name of the schema where that type (or domain) is. For example, this query: ``` SELECT a.attname, d.adsrc FROM pg_attribute a LEFT JOIN pg_attrdef d ON a.attrelid = d.adrelid AND a.attnum = d.adnum WHERE a.attrelid = "defaults"'::regclass AND a.attnum > 0 AND NOT a.attisdropped ORDER BY a.attnum; ``` could return something like "'<default_value>'::pg_catalog.text" or "(''<default_value>'::pg_catalog.text)::text" for the text columns with defaults. I modified the regexp used to parse this value so that it ignores anything between ':: and \b(?:character varying|bpchar|text), and it allows to have optional parens like in the above second example.
-
由 Rafael Mendonça França 提交于
Clean up Gemfile entry (replace double quotes with single quotes) [ci skip]
-
由 Lee Reilly 提交于
-
由 Jeremy Kemper 提交于
-
- 13 10月, 2012 11 次提交
-
-
由 Joshua Peek 提交于
-
由 Joshua Peek 提交于
-
由 Jeremy Kemper 提交于
-
由 Jeremy Kemper 提交于
-
由 Jeremy Kemper 提交于
Remove the queue container. Premature consolidation. Set up and maintain queues in the classes that use them instead.
-
由 José Valim 提交于
Prompt to run rake when accidentally typed rails
-
由 Aaron Patterson 提交于
Before: Calculating ------------------------------------- ar 87 i/100ms ------------------------------------------------- ar 823.4 (±11.8%) i/s - 4089 in 5.070234s After: Calculating ------------------------------------- ar 88 i/100ms ------------------------------------------------- ar 894.1 (±3.9%) i/s - 4488 in 5.028161s Same test as 3a6dfca7
-
由 Aaron Patterson 提交于
before: Calculating ------------------------------------- ar 83 i/100ms ------------------------------------------------- ar 832.1 (±4.0%) i/s - 4233 in 5.096611s after: Calculating ------------------------------------- ar 87 i/100ms ------------------------------------------------- ar 839.0 (±9.3%) i/s - 4176 in 5.032782s Benchmark: require 'config/environment' require 'benchmark/ips' GC.disable unless User.find_by_login('tater') u = User.new u.login = 'tater' u.save! end def active_record user = User.find_by_login('tater') starred = user.starred_items.count end active_record Benchmark.ips do |x| x.report("ar") { active_record } end
-
由 schneems 提交于
Developers from all levels will accidentally run rake tasks using the `rails` keyword when they meant to use `rake`. Often times beginners struggle with the difference between the tools. The most common example would be `$ rails db:migrate` Rather than telling the developer simply that they did not use a valid rails command, we can see if it was a valid rake command first. If it is a valid rake command we can auto execute it giving the user a period of time to cancel if that isn't what they intended. Here is what `rake db:migrate` would look like if you cancel the command: ```sh $ rails db:migrate Assuming you meant: $ rake db:migrate press any key to cancel in 3 seconds > command terminated ... ``` Here is what it looks like if you don't cancel the command: ```sh $ rails db:migrate Assuming you meant: $ rake db:migrate press any key to cancel in 3 seconds > Running: $ rake db:migrate == Foo: migrating ============================================================ == Foo: migrated (0.0000s) =================================================== ```
-
由 Joshua Peek 提交于
-
由 Joshua Peek 提交于
-