http://blog.gmane.org/gmane.comp.lang.ruby.rails.core hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.lang.ruby.rails.core/10639 Re: github.com/rails/rails/commit/3b3c05 Says process scripts were extracted to github.com/rails/irs_process_scripts, but that repo hasn't been pushed to. Did DHH forget? What was the reason for this change; because it wasn't portable (unix only)? Has it something to do with moving over to Rack? Default Capistrano recipe kinda relies on these and I use them in most of my projects that aren't on Passenger. Thanks, # Mislav --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core< at >googlegroups.com To unsubscribe from this group, send email to rubyonrails-core+unsubscribe< at >googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~--- Mislav Marohnić 2008-12-01T10:05:28 http://comments.gmane.org/gmane.comp.lang.ruby.rails.core/10638 Hello, For an internal project we were looking for a solution which extends ActiveRecord by an iterator function. Using find(:all) is no fun if you have to process some 10.000 records. Until now there have been two ways of dealing with that scenario: - write your logic a second times (e.g. use stored procedure) - bet on AR plugins which work around that limitation by fetching IDs and processing them in groups, or by using :offset and :limit Rewriting logic is something we wanted to avoid, and the plugins don't fully respect transactional contexts. So we started to implement our own true iterator support for AR. Our project is on Oracle, but in the meantime we have added support for MySQL. Probably other adapters can be extended easily, too. We also tried JRuby 1.1.x, which is sometimes faster than Ruby 1.8.6, but a patch is needed to bring the Java part of the connection adapter into shape for a result set iteration. Okay, you're about to ask: how does it work. Here we go: MyTable.find_each_by_ Andreas Gungl 2008-11-29T14:14:00 http://comments.gmane.org/gmane.comp.lang.ruby.rails.core/10637 Hi, I've started looking at the counter_cache implementation with the original intention to have the increment, decrement update the model in memory (without relying on a reload) to be called. You can see a sample of the bug here: http://gist.github.com/30580. While starting to look at this issue (my first real look at the rails code base) I'm wondering if anyone has already done any initial thinking of this issue or has an idea of what they would like to see happen here. In my initial thinking (I haven't looked at the association proxy/collection enough) there could be a bi-directional link for the has_many/belongs_to reflections/assocations. Looking around I noticed a small bug with custom counter cache names not be utilized in the record with the has_many association. There is currently no way for this association/reflection object to know about the belongs_to settings where the counter_cache name is set. An easy way to quickly solve this is to add a :counter_cache => 'custom_name' to the has_many adamc 2008-12-01T02:15:15 http://comments.gmane.org/gmane.comp.lang.ruby.rails.core/10633 Hi all, New in Rails 2.2 is a check to determine if the mail server responds to enable_starttls_auto. I submitted a patch for this Lighthouse ticket: http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/1491 This is my first Rails patch submission, so any comments, suggestions or criticisms are greatly appreciated. Thanks, Dan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core< at >googlegroups.com To unsubscribe from this group, send email to rubyonrails-core+unsubscribe< at >googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~--- Dan Ryan 2008-11-29T04:40:16 http://comments.gmane.org/gmane.comp.lang.ruby.rails.core/10632 I've created a patch in lighthouse for this and looking for a bit of feedback. Essential the problem is due to MySQL (and perhaps other database vendors) of returning an empty result set for: select * from somewhere where name in (null) regardless of whether there are records with null entries in that field. the version that does work is: select * from somewhere where name is null with active record this means that the following does not return the expected records: Event.find(:all, :conditions => {:venue_id => [1,2,nil]}) http://rails.lighthouseapp.com/projects/8994/tickets/1486-active-record-conditions-to-deal-with-nils-in-arrays cheers, n --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core< at >googlegroups.com To unsubscribe from this group, send email to rubyonrails-core+unsubscribe< at >googlegroups.com For more options, visit this group at http: Nick Sellen 2008-11-29T02:17:03 http://comments.gmane.org/gmane.comp.lang.ruby.rails.core/10631 Hello, I ran into a problem recently that was previously reported as ticket #802 [1]. The issue, briefly, occurs when a model definition runs a class method (such as for a plugin) that checks table information. In this case, loading the model requires the database table to already exist. Running `rake db:migrate` in staging or production (anywhere with config.cache_classes=true) will then try and eager load all application classes, quickly failing with a table-not-found sort of error. Also, the eager loading seems pretty detrimental any time Rails is booted from the console, such as via `script/runner` or `rake db:migrate`. Not only can it blow up because of an unmigrated database, but it incurs a pretty senseless performance hit for what may be a simple task. This could really hit applications that use BJ to run jobs in a full Rails environment, for example. Does anyone have ideas how Rails might be smarter about when to eager load? -Lance [1] http://rails.lighthouseapp.com/projects/8994-ruby-on-rails cainlevy 2008-11-29T01:51:50 http://comments.gmane.org/gmane.comp.lang.ruby.rails.core/10629 Consider the following example. class Project has_many :tasks end class Task belongs_to :project end < at >project = Project.find(1) < at >project.task.find(1) < at >project.task.build(params[:task]) < at >project.task.delete(params[:task_id]) In all these cases < at >project is needed. actually we need only project_id for all the above things. If the below given things are possible the would save us from the query < at >project = Project.find(1) Project.task.find(project_id,task_id) Project.task.build(project_id,params[:task]) Project.task.delete(project_id,params[:task_id]) If this thing can be added to rails it would be great. Regards, Pankaj --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core< at >googlegroups.com To unsubscribe from this group, send email to rubyonrails-core+unsubscribe< at >googlegroups.com For more options, visit this group at http://groups.google.com/gro pankaj 2008-11-28T09:29:51 http://comments.gmane.org/gmane.comp.lang.ruby.rails.core/10625 I like assert_difference, but I find the error messages slightly unhelpful when I'm verifying more than one thing. Suppose something should create both a new customer and a question, I could write assert_difference 'Question.count' do assert_difference 'Customer.count' do ... end end Unlike a normal assertion the test line causing the failure will be a few lines down the stack trace so it's not obvious to me with a quick glance which of the assertions have failed (although this is fixable by providing a custom failure message). I'd rather write assert_difference ['Question.count', 'Customer.count'] do ... end but if a failure occurs here then I genuinely don't know which assertion has failed (unless I can remember that 'expected 4 got 3' must be talking about the customer assertion because I remember the number of records defined in the fixtures). It seems to me that this could be made more helpful if the default error message included the expression being evaluated eg something along the li Frederick Cheung 2008-11-27T11:38:15 http://comments.gmane.org/gmane.comp.lang.ruby.rails.core/10618 Hi all Just spotted a issue when using the json & activesupport gems in the same project. Below is a simple irb session showing the effect: irb(main):001:0> require 'json' => true irb(main):002:0> Time.now.to_json( nil, 1 ) => "\"Wed Nov 26 15:56:02 +0200 2008\"" irb(main):003:0> require 'activesupport' => true irb(main):004:0> Time.now.to_json( nil, 1 ) ArgumentError: wrong number of arguments (2 for 1) from (irb):4:in `to_json' from (irb):4 Searching through the json_pure-1.1.3 code it seems the #to_json signature is "def to_json(*)", and in activesupport's Time it's def to_json(options = nil). Looking through the other activesupport extensions for JSON it seems to be the same case. Any suggestions? Any objections to me diving in and fixing it? Best Kenneth Kalmer 2008-11-26T14:08:35 http://comments.gmane.org/gmane.comp.lang.ruby.rails.core/10612 I've run into the following issue: My app has multiple users from multiple timezones. In the majority of cases, I want datetime columns to take into account the user's timezone. This works fine. However, for *one* particular datetime field, I want users to enter the arrival date & time of a flight that is arriving into a country in a different timezone to the user's timezone. Hence I don't want any timezone conversion done on this particular field. e.g. a user in Germany enters the data for a flight that will arrive in New Zealand on January 1st at 2:00pm. When a different user views this data, I want it to say 2:00pm, regardless of the user's timezone. I don't see that the datetime_select helper allows me to specify a timezone for the time I am selecting; but anyway, I don't want the user to have to enter a timezone. I suppose the easiest (only?) solution is to store the data in separate date and time fields in the database, and use separate date_select and time_select helpers. Any comments? Should Dave Rothlisberger 2008-11-26T00:42:59 http://comments.gmane.org/gmane.comp.lang.ruby.rails.core/10609 I'm writing a rails plugin, and figured I'd do it as a GemPlugin to be ahead of the curve. I need to install some assets when the plugin is installed in a rails app, but it would seem there's no mechanism by which this occurs; install.rb is never run for a GemPlugin, unless I'm missing something entirely. I could check for the assets in init.rb and copy them over if they don't exist, but that strikes me as poor behavior. I would guess the thing to do would be to create a new gems task, gems:plugin:install or similar, which would invoke the install scripts on all config.gems that have been tagged with :plugin => true. Before I dive in and give this a whirl, though, I figured I'd check with the dev team and see if a. I've overlooked an existing installation mechanism, b. someone already had something in the works, or even c. the GemPlugin idea was still considered to be the future of plugins, or if yet another strategy was being considered. - donald --~--~---------~--~----~------------~-------~--~----~ You Donald Ball 2008-11-25T19:59:53 http://comments.gmane.org/gmane.comp.lang.ruby.rails.core/10603 I've added a patch to the "'IP spoofing attack' breaks with some proxies" discussion. http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/1200 The patch is a workaround to the issue, since the real problem is poorly configured proxies, which can't be patched in Rails. Our site, which has a lot of WAP traffic, generates massive amounts of false positive "Spoofing Checks." To date, we've been monkey patching rails to remove that check, but I think the change I've suggested is a reasonable compromise. Thanks, Darren --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core< at >googlegroups.com To unsubscribe from this group, send email to rubyonrails-core+unsubscribe< at >googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~--- Darren 2008-11-22T18:27:36 http://comments.gmane.org/gmane.comp.lang.ruby.rails.core/10602 The discussion on #553 in Lighthouse got me thinking - would it be useful to enable vendored gems to be git repos? WIth many gems moving to github, most have a working copy of the gemspec in the repo. For instance, a trunk copy of, say, attribute_fu could be dropped into vendor/gems with git clone git://github.com/giraffesoft/attribute_fu.git vendor/gems/ attribute_fu My first thought was that this might be very useful for gem developers... It would be straightforward to implement, but does it sound useful? Thanks, --Matt Jones --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core< at >googlegroups.com To unsubscribe from this group, send email to rubyonrails-core+unsubscribe< at >googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~--- Matt Jones 2008-11-25T05:57:30 http://comments.gmane.org/gmane.comp.lang.ruby.rails.core/10592 Hey guys, I've just committed a change to the way we generate and use CSRF tokens in rails[1]. Instead of all the stuff involving :secret and session ids, we simply take advantage of ActiveSupport::SecureRandom. This simplifies the tests and code drastically, and shouldn't have any negative impact on security. Any feedback or reports of breakage greatly appreciated. Also, thanks to Adam Barth and Colin Jackson of Stanford for taking the time to verify the approach with me. [1] http://github.com/rails/rails/commit/9fdb15e60f4d4e37916e5354c50d559773bbe014 Michael Koziarski 2008-11-23T14:07:03 http://comments.gmane.org/gmane.comp.lang.ruby.rails.core/10591 I've begun implementing an API for installing, updating and removing plugins. This will allow for pluggable plugin managers, e.g. to support other version control systems than those built into Rails. I haven't got a lot of expertise in this area, so if anyone has some good comments on the design/approach, please say so. My current design is this: A plugin manager, e.g. GitPluginManager, inherits from PluginManager::Base. It can override #install, #update and #remove. It hooks into a URI scheme (e.g. "git://...") by calling PluginManager.add_plugin_manager(uri_scheme, manager). PluginManager.install(uri[, options]) installs the plugin identified by the URI. Behind the scene, a suitable plugin manager is found, and its #install method is called. PluginManager.update(name[, options]) updates the named plugin (e.g. "acts_as_awesome"). I have not begun work on this yet. PluginManager.remove(name[, options]) removes the named plugin. Behind the scenes, PluginManager finds out which plugin manager has instal Daniel Schierbeck 2008-11-22T20:47:01 http://comments.gmane.org/gmane.comp.lang.ruby.rails.core/10586 I'm working on a plug-in that will allow has_many associations to ignore the foreign key. This may sound silly, but there are situations where you'd like to join on something other than a single foreign key. Right now, I can configure :conditions for the association, but these are in addition to the existing foreign key. My plug-in would do something akin to http://pastie.org/319143. This is really just pseudo-code, I haven't tested it yet. So, two questions: - Am I the only one crazy enough to think something like this is useful? - How can a plugin monkey-patch ActiveRecord for this? Just override the entire construct_sql method? Thanks for any advice, Norman --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core< at >googlegroups.com To unsubscribe from this group, send email to rubyonrails-core+unsubscribe< at >googlegroups.com For more options, visit t Norm 2008-11-19T21:47:57 http://comments.gmane.org/gmane.comp.lang.ruby.rails.core/10584 Hi all, To quote the radio, "Long time listener, first time caller." I just put a ticket in Lighthouse with a patch to fix a fairly serious bug in the AR habtm association preloading SQL. It doesn't affect mysql or postgres; only Oracle. Essentially, the preloading generates something like the following: SELECT developers.*, t0.project_id as _parent_record_id FROM developers INNER JOIN developers_projects as t0 ON developers.id = t0.developer_id WHERE (t0.project_id IN (1,2)) The problem is that, in standard SQL, "INNER JOIN developers_projects as t0" is invalid. "INNER JOIN developers_projects t0" is the standard notation. Many dbs just deal with the extra "as" but Oracle doesn't. Looking for some +1 loving. Thanks! http://rails.lighthouseapp.com/projects/8994/tickets/1405-patch-fixed-non-standard-sql-generated-by-preloading-has_and_belongs_to_many-associations Brent --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "R Foliosus 2008-11-19T19:10:50 http://comments.gmane.org/gmane.comp.lang.ruby.rails.core/10583 Just wondering if there are any issues with the following patch... http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/1418 I was trying to pass :encode => :hex to my auto generated email addresses and realized this wasn't possible. This patch allows options to be passed to a mail_to link. Thanks, Andrew --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core< at >googlegroups.com To unsubscribe from this group, send email to rubyonrails-core+unsubscribe< at >googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~--- Andrew Kaspick 2008-11-19T19:04:08 http://comments.gmane.org/gmane.comp.lang.ruby.rails.core/10581 While upgrading an app to 2.2.1 I noticed a change in the behavior of serialized attributes in ActiveRecord. I have an AR model with a serialized attribute which is used to store either a fixnum of an array of fixnums. Previously, a single fixnum stored in this attribute would be returned as a fixnum, however since a recent commit [1] it is now returned as a string. I'm not sure whether is a typical use case, but it doesn't seem like expected behavior. I started looking at creating a patch but it became non-trivial as I strayed off into ActiveRecord::ConnectionAdapters::Quoting. So instead, I thought it better I get some feedback here. Cheers, Paul [1] http://github.com/rails/rails/commit/c94ba8150a726da4a894cd8325ee682a3286ec9f --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core< at >googlegroups.com To unsubscribe from this group, send email to rubyo Paul Horsfall 2008-11-19T15:12:28 http://comments.gmane.org/gmane.comp.lang.ruby.rails.core/10579 When Rails try to generate <% form_for(< at >product) do |f| %> for an ActiveResource::Base Product, it's failed like that : product_url failed to generate from {:action=>"show" ... and with move to 2.1.2 and restart mongrel, it's work well. Kind Regards --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core< at >googlegroups.com To unsubscribe from this group, send email to rubyonrails-core+unsubscribe< at >googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~--- Joel Azemar 2008-11-18T13:44:32 http://comments.gmane.org/gmane.comp.lang.ruby.rails.core/10576 I know I can configure Rails.cache to be backed by memcache, and that I can configure multiple memcache servers for load balancing. Is there any way to configure multiple instances of Rails.cache? In this case, I'd like my application to use a standard memcache server, as well as a starling server. Ideally, something like Rails.cache[:memcache] vs. Rails.cache[:starling] would point to different servers. Thoughts? Thanks! Norman --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core< at >googlegroups.com To unsubscribe from this group, send email to rubyonrails-core+unsubscribe< at >googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~--- Norman Elton 2008-11-18T21:54:21 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.lang.ruby.rails.core