Marcel Molina Jr. wrote:
Taken care of in http://dev.rubyonrails.org/changeset/4315. Thanks for
mentioning it.
Sweet.
--
John Long
http://wiseheartdesign.com
___
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/ma
I'm getting the following in schema.rb when I rake db:schema:dump:
# Could not dump table "config" because of following NameError
# uninitialized constant StringIO
The problem goes away if I add "require 'stringio'" to boot.rb. Is this
a known issue?
--
John Long
http://wiseheartdesign.com
Rick Olson wrote:
http://dev.rubyonrails.org/changeset/4239
Thanks Rick.
--
John Long
http://wiseheartdesign.com
___
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core
Rick Olson wrote:
Yup, go for it. Post the ticket # and I'll see about adding it. I'd
appreciate any folks using mssql, oracle, etc to try it out too.
Rick, any word on this?
--
John Long
http://wiseheartdesign.com
___
Rails-core mailing list
Rails
Rick Olson wrote:
Brilliant. So I should patch schema_statements.rb to use
#quote_column_name in #add_index?
Yup, go for it. Post the ticket # and I'll see about adding it. I'd
appreciate any folks using mssql, oracle, etc to try it out too.
Done:
http://dev.rubyonrails.org/ticket/4764
Rick Olson wrote:
And the problem went away. Is this just a MySQL issue or would the
problem be common across all databases? I would like to submit a patch
for this if I can. Are there other places that would benefit from
backticks to avoid problems which occur because key words are used as
table
The upgrade to Rails 1.1 hurt my ability to run tests because it
generated the following MySQL error:
Mysql::Error: You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the right syntax to
use near 'key ON config (key)' at line 1: CREATE
Rick Olson wrote:
Setup of course creates a new controller, request, etc... Has something
changed in the upgrade to 1.1 that would effect multiple process calls
in a controller test?
New controller instances are created on each request anyway. I try
not to do multiple controller requests in a
While upgrading to Rails 1.1 one of my tests started failing which
wasn't failing before:
def test_developer_action__not_allowed_if_other
@developer_actions.each do |action|
get action, { :id => 1 }, { :user => users(:existing) }, {}
assert_redirected_to page_index_url, "action:
I wonder if something like this would make a good addition to the core:
http://wiseheartdesign.com/articles/2006/01/28/test-helpers-for-rails
It seems a useful and helpful convention.
--
John Long
http://wiseheartdesign.com
___
Rails-core mailing list
10 matches
Mail list logo