search for: metaskills

I''ve seen a few examples of dummy Rails apps (for testing, so they live under test or spec dirs, typically) for use with the Appraisals gem that supposedly work with both Rails 3.x and Rails 4, but they seem hackish and not fully functional. It is somewhat expected, as it is a stripped down Frankenstein monster that is trying to be compatible with various versions of Rails 3 as well

Any quick tips? I''ve been getting the SQL Server adapter up to passing for 3.2 and I wanted to test our explain printer. It will be very much like mysql2''s printer. But I think my brain is mush and my meta-fu weak at the moment and I need some help. I tried stubbing ActiveRecord::Base.logger.warn but to no avail. Any thoughts? - Ken -- You received this message because you

...t is really just a few lines of code [2]. I''d be willing to submit a patch if you think this is helpful. I could easily check to see if the version of MiniTest supports the method chain interface to make this happen or take other advice. I found it really helpful :) [1] https://github.com/metaskills/mini_backtrace [2] https://github.com/metaskills/mini_backtrace/blob/master/lib/mini_backtrace/unit.rb - Thanks, Ken -- 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@go...

I''m looking for a simple way to integrate minitest/spec with Rails 3.1. Anybody have it working? There''s an older article on MetaSkills about this but it adds stuff I don''t want. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this...

Not getting any love (tender or otherwise) on my pull request<https://github.com/rails/rails/pull/7035>so I thought you folks might like to chip in. What do you think? #cast and #cast! allow you to declare a mapping from generated column names to simplified database column types (i.e. those used in migrations). This way scopes with columns generated in their select lists can also include

Can someone please post or refer to detailed instructions for getting Rails going on Snow Leopard with ODBC to a MS SQL server? The Rails Wiki is pretty bad and I can''t seem to get it going! Thanks, Tom

Every now and then when I am working on making the SQL Server adapter pass all the ActiveRecord tests, I notice one that looks like a false positive in the core DBs. Here is one case in relations_test.rb. Can someone look at this and just tell me it is normal for other DBs and just odd for SQL Server? Or maybe it is just my understand of some SQL standard. I''m really not that SQL smart.

When calls were made to test 3.0.4.rc1, I followed up a few days afterward for the latest SQL Server adapter. Santiago was nice enough to pick up on my ticket for a calculation bug [1] and got it committed to master [2] and then 3-0-stable [3] so it can make it in the next release. I just ran my test suite on the tag of the repo and it appears these did not make it in the v3.0.4 release. How did

Hi guys. I''m using a postgreSQL with multiple schemas. To change between schemas I use the ''SET schema TO ...'' statement. That works ok in rails 3.0. Rails 3.1 uses prepared statements and does not take into account the ''schema_search_path''. This is a big problem because the statement is prepared once and then the same prepared statement is executed

In 2fe70c1 (last year), rails changed from a static list of assets.paths to automatically register any path under assets/*. (This was not reflected in Rails Guides so I pushed an update to docrails.) However, in my opinion, these automatic asset paths create confusion. The result is that the first-level directories under `(app|lib|vendor)/assets` get swallowed and if I put assets into a

Lighthouse ticket: https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/4452 I have recently been working on some gems that utilize ActiveSupport::Cache and ran into some issues with the different implementations handling the same functionality differently. One of the issues was that I couldn''t rely on expiring entries with the :expires_in option. MemCacheStore takes this

Greetings, I am curious, I see quite a few references to using TextMate for rails development. I downloaded TextMate and used it for 30 days. I do not see what everyone is raving about. Snipplets are nice, but other editors do the same thing, some with much more power. Can anyone tell me what makes people draw to TextMate? Maybe I am missing the whole reason, I''d really like to

I''ve successfully created a super long link_to_remote() in my view template that has lots of AJAX call backs to update my page. I want to put these into RJS templates, but I can not figure out how to do so. Are things like :loading, :success, :failure, :complete moot when using RJS because this is the logic you put into the action from the link_to_remote? - TIA, Ken

I was just learning about the "in_place_editor_field" tag when reading thru RAILs Recipes. What is "in_place_editor_options" for???? I was hoping after reading the script.aculo.us documentation that I could do something like this. <%= in_place_editor_field :contact, column.name, {:tag => ''div''}, { :cancelText => ''Never

[using RAILs 1.1.2] Has anyone else seen issues where multiple tiered "acts_as_list" models do not CASCADE delete correctly? For instance, I have 4 models, the first 3 in the hierarchy have the appropriate "have_many" declarations with "exclusively_dependent => true". The last the models have the appropriate "acts_as_list" with the correct scope

I''ve been reading up in ActiveRecord::Associations and playing around with my app via the console and found some interesting methods via the code completion of IRB, but I have no idea how to use them and can only find one hint in the API http://api.rubyonrails.com/classes/ActiveRecord/Associations/ ClassMethods.html It mentions here in the has many associations that if you use the

I could not find the answer to this in a few Google searches and thought I would ask. So when are prepared statements best leveraged in ActiveRecord''s interface? I never really noticed before, but simple condition hashes or scopes do not pass down the binds so that prepared statements are leveraged. So a `Car.find(1)` would but things like `Car.where(:id => 1).first` do not. Is it a