aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* use prepared statements for primary key queriesAaron Patterson2011-04-111-2/+15
|
* last insert id can never be called, so remove that code pathAaron Patterson2011-04-111-11/+3
|
* we know the table and pk, so we can calculate a default sequence nameAaron Patterson2011-04-111-3/+4
|
* always look up pk and sequence unless both are providedAaron Patterson2011-04-111-6/+5
|
* pg does not know the insert_id in advance, so super will never return trueAaron Patterson2011-04-111-13/+10
|
* updating the docco for ActiveRecord::ResultAaron Patterson2011-04-111-2/+2
|
* implement exec_query on mysql2 adapterAaron Patterson2011-04-111-2/+20
|
* make sqlite insert_sql more consistent with other adaptersAaron Patterson2011-04-111-1/+2
|
* adding exec_insert for postgresqlAaron Patterson2011-04-113-1/+43
|
* fixing variable name in mysql testAaron Patterson2011-04-111-1/+1
|
* properly name schema queries for the loggerAaron Patterson2011-04-111-10/+10
|
* adding mysql adapter test caseAaron Patterson2011-04-111-0/+69
|
* adding client_encoding method for discovering the encoding set for this ↵Aaron Patterson2011-04-111-0/+62
| | | | client, testing exec_insert on a string
* properly name schema queries for loggingAaron Patterson2011-04-111-3/+3
|
* adding exec_insert to sqlite3Aaron Patterson2011-04-112-0/+16
|
* adding a case_sensitive_modifier for forcing comparisons to be case sensitiveAaron Patterson2011-04-114-0/+15
|
* only support pg >= 8.2, so no need to checkAaron Patterson2011-04-111-7/+4
|
* Remove code duplication.José Valim2011-04-113-20/+27
|
* No need to rescue here. Invoking the wrong method in an object can happen ↵José Valim2011-04-116-40/+0
| | | | anywhere if you are not careful. In other words, test your shit.
* Revert "Add :use_include option to allow user to explicitly use ↵José Valim2011-04-114-37/+14
| | | | | | | | `Range#include?` method in Ruby 1.9" Use :with => range.to_a instead. This reverts commit f6540211b5b9133c9f93c11655a04d613c237e67.
* Keep the same API semantics for update/delete as we had for XML (just return ↵David Heinemeier Hansson2011-04-111-2/+2
| | | | 200 OK, no body)
* Cant use inclusion in commands/application.rb as the frameworks havent all ↵David Heinemeier Hansson2011-04-112-2/+2
| | | | been required yet
* pg should define insert_sql so that query cache actually works for insertsAaron Patterson2011-04-101-2/+1
|
* Fix failing test case on masterPrem Sichanugrist2011-04-102-2/+2
| | | | It turned out that I overlook at some replacements ..
* adding pg support notes to the changelogAaron Patterson2011-04-101-0/+2
|
* community support for pg < 8.2 has ended, so we can drop support for those ↵Aaron Patterson2011-04-101-62/+12
| | | | versions
* Refactored uniqueness validator to use Arel instead of hardcoded SQLBrian Cardarella2011-04-101-26/+11
|
* Using Object#in? and Object#either? in various placesPrem Sichanugrist2011-04-1144-52/+108
| | | | There're a lot of places in Rails source code which make a lot of sense to switching to Object#in? or Object#either? instead of using [].include?.
* Add support for Object#in? and Object#either? in Active Support [#6321 ↵Prem Sichanugrist, Brian Morearty, John Reitano2011-04-113-0/+74
| | | | | | | | | | | | state:committed] This will allow you to check if an object is included in another object or the list of objects or not. This patch is derived from patch by Brian Morearty and John Reitano on Lighthouse ticket. I've rewrite it and make sure that we support both 'another object' and 'list of objects' version, as it surely be useful to support both.
* Remove dead branch code that appeared back in a merge.José Valim2011-04-101-6/+0
|
* Add :use_include option to allow user to explicitly use `Range#include?` ↵Prem Sichanugrist2011-04-104-14/+37
| | | | | | method in Ruby 1.9 In Ruby 1.9 we're currently use `Range#cover?` to fix the performance problem. However, there might be the case that you want to use `Range#include?` instead. This patch will give you that option.
* Add support for proc or lambda as an option for InclusionValidator, ↵Prem Sichanugrist2011-04-107-20/+167
| | | | | | ExclusionValidator, and FormatValidator You can now use a proc or lambda in :in option for InclusionValidator and ExclusionValidator, and :with, :without option for FormatValidator
* Add --old-style-hash option to force creating old style hash on Ruby 1.9Prem Sichanugrist2011-04-105-2/+25
| | | | That means if you don't like the new syntax, you can pass --old-style-hash to force Rails to generate code with hash rockets.
* Rails will now generate Ruby 1.9 style hash when running app generator on ↵Prem Sichanugrist2011-04-105-4/+23
| | | | | | Ruby 1.9.x The new hash syntax of Ruby 1.9 looks more superior, so we decide to switch to it in the places that appropriate.
* Rails will now generate Ruby 1.9 style hash when running scaffold_controller ↵Prem Sichanugrist2011-04-106-19/+50
| | | | | | | | generator on Ruby 1.9.x The new hash syntax of Ruby 1.9 looks more superior, so we decide to switch to it in the places that appropriate. This patch has been requested by DHH.
* Make scaffold_controller generator generate code for JSON response instead ↵Prem Sichanugrist2011-04-102-14/+16
| | | | | | | | of XML It seems like a lot of people are using JSON in their API more than XML nowadays, so Rails should follow that convention by providing the JSON format block in scaffold_controller by default. This patch has been requested by DHH
* moving sqlite_adapter_tests to sqlite3_adapter_test so that the tests are ↵Aaron Patterson2011-04-082-229/+215
| | | | actually run. :bomb:
* make turn a soft dependency. generate a Gemfile that contains turn and ↵Aaron Patterson2011-04-083-7/+14
| | | | require turn if it is available
* Make csrf_meta_tags use the tag helperJames Robinson2011-04-082-9/+9
| | | | Improved formatting of csrf_helper and improved test coverage
* Merge branch 'master' of github.com:rails/railsAaron Patterson2011-04-072-4/+4
|\ | | | | | | | | | | | | | | | | | | * 'master' of github.com:rails/rails: Cache flash now Revert "Use freeze instead of close!" Revert "Eagerly load Signed and Permanent cookies" cookies here Eagerly load Signed and Permanent cookies Use freeze instead of close!
| * Cache flash nowSantiago Pastorino2011-04-071-1/+1
| |
| * Revert "Use freeze instead of close!"Santiago Pastorino2011-04-073-11/+14
| | | | | | | | This reverts commit 29592a7f09dda2e7e1e0a915d9230fe6a9b5c0af.
| * Revert "Eagerly load Signed and Permanent cookies"Santiago Pastorino2011-04-071-17/+10
| | | | | | | | This reverts commit dffeda377021ba8691381195f5a2889f8e040b93.
| * cookies hereSantiago Pastorino2011-04-071-3/+3
| |
| * Eagerly load Signed and Permanent cookiesSantiago Pastorino2011-04-071-10/+17
| |
| * Use freeze instead of close!Santiago Pastorino2011-04-063-14/+11
| |
* | many args does not make sense with the current implementation because of how ↵Aaron Patterson2011-04-061-10/+0
| | | | | | | | `use` works
* | getting the flash hash under testAaron Patterson2011-04-062-0/+104
| |
* | favor composition over inheritance, have FlashHash delegate to a HashAaron Patterson2011-04-062-11/+44
|/
* CookieJar should prefer composition over inheritanceAaron Patterson2011-04-061-6/+10
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-02 19:43:40 +0000