https://github.com/brianmario/yajl-ruby
Yajl is capable of doing it. So hacking together Yajl and
ActionController::Live
might give you streaming json as it is produced.
Robert Pankowecki
--
You received this message because you are subscribed to the Google Groups Ruby
on Rails: Core group
What is the usecase? What value does it provide ? How is it any better than
?
def title; nil; end
def type; nil; end
Maybe it is just me but I totally do not get what your are trying to
achieve.
Robert Pankowecki
--
You received this message because you are subscribed to the Google Groups
Probably because of the way how Rails is looking for constants ? I would
guess that it does not read the file from engine at all, and just reads the
file from your app.
Robert Pankowecki
http://robert.pankowecki.pl
On Fri, Sep 28, 2012 at 12:59 PM, Luís Ferreira zamith...@gmail.com wrote:
Hey
Proposed alternative:
production:
uri: postgres://username:passw...@database.host.com:5432/production_db
pool: 5
Alternative:
production:
postgres://username:passw...@database.host.com:5432/production_db?pool=5
Robert Pankowecki
http://robert.pankowecki.pl
--
You received
On Mon, Sep 24, 2012 at 4:29 PM, Fabian Becker
fabian.becke...@gmail.com wrote:
What makes that solution better than the current (more readable) version?
It is less verbose I guess. Also java, .net and mongo use/support
connection strings.
Robert Pankowecki
--
You received this message
MyProject::Journey
def self.model_name
@model_name ||= ActiveModel::Name.new ::Journey
end
end
I am not sure if that would work perfectly but you can give it a try.
Robert Pankowecki
http://robert.pankowecki.pl/
--
You received this message because you are subscribed to the Google Groups
I sometimes use flash to keep things between multiple request ex.
searched word and use FlashHash#keep in before filter to keep it when
user is still using the same controller. How can I keep something for
the next request when rendering in your proposed solution? Would I
have to set flash and
'
Works fine for me.
i.e., keep the common case clean, at the expense of making the unusual case
a bit more work.
I agree. Just didn't want the unusual case to be impossible after some
refactoring.
Thanks for your input. :)
You are welcome.
Robert Pankowecki
--
You received this message
If you have time, just do it please :) Lot of people will be grateful. Be
aware that thread parallelization (probably most obvious and simple
solution) won't give us any benefit on MRI.
Robert Pankowecki
--
You received this message because you are subscribed to the Google Groups Ruby
on Rails
PostsToDasherize.all.each{|p| p.dasherize! } # Use batches instead
end
end
def self.down
# ...
end
end
Robert Pankowecki
--
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@googlegroups.com
Or you can just symlink staging.rb to production.rb. But I would never
risk a mistake coming from fact that the entry in my database.yml for
staging would be called production.
Robert Pankowecki
--
You received this message because you are subscribed to the Google Groups Ruby
on Rails: Core
controller:
[:deleted, :disabled].each{|p| model.send :#{p}=, params[p] == 'true' }
model.update_attributes(params.slice(:deleted, :disabled)).
And let your model handle the conversion of attribute values.
Robert Pankowecki
--
You received this message because you are subscribed to the Google
RC releases are very important. If you don't want to use them (don't care
about them), fine. I found few bugs in RC versions and used veto to
reschedule their release. All of that with simply changing my Gemfile and
running rake test.
Robert Pankowecki
--
You received this message because you
On Wed, Oct 12, 2011 at 11:53 PM, Will Bryant will.bry...@gmail.com wrote:
You can turn transaction fixtures off for an individual set of tests though
Exacyly what I mean.
class Test ActiveSupport::TestCase
self.use_transactional_fixutures = false
end
--
You received this message because
What's wrong with turning off transactional fixtures in the tests that
check after_commit/after_rollback functionality ? You can check what
you need and clean the db yourself in the test or teardown.
Robert Pankowecki
--
You received this message because you are subscribed to the Google Groups
Which exception would you raise if 2 validations fail ?
Robert Pankowecki
--
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@googlegroups.com.
To unsubscribe from this group, send email
Is there somewhere a list of names that should not be used as action names ?
I recently created an action named load and it disappeared from inherited
controller.
Would such a list be equal to : AbstractController::Base.internal_methods ?
Robert Pankowecki
http://robert.pankowecki.pl
--
You
Works fine for me thanx to ecom.rb
module Ecom
def self.table_name_prefix
'ecom_'
end
end
make sure that you have
class Ecom::Cart ActiveRecord::Base
end
instead of
module Ecom
class Cart ActiveRecord::Base
end
end
in your ecom/cart.rb
Robert Pankowecki
http
I think it is done this way to easily overwrite table_name_prefix for all
tables of namespaced models. And when it comes to decision making process I
know nothing about it so I cannot help you with that question.
Robert
--
You received this message because you are subscribed to the Google
3.0.8.rc3 had this Syck issue :
https://github.com/rails/rails/issues/1412 which is a mystery for me
however 3.0.8.rc4 works fine for me! :-)
Robert Pankowecki
--
You received this message because you are subscribed to the Google Groups Ruby
on Rails: Core group.
To post to this group, send
Current 3-0-8 branch works fine for me now :-)
Robert Pankowecki
--
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@googlegroups.com.
To unsubscribe from this group, send email
https://github.com/rails/rails/issues/1402
Can we expect support for that in Rails 3.1.0 ?
Robert Pankowecki
--
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@googlegroups.com
This https://github.com/rails/rails/issues/1322 is not fixed in 3.0.8.rc2 :-(
I'm still getting the same error.
Robert Pankowecki
--
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
Double veto:
https://github.com/rails/rails/issues/1326
--
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@googlegroups.com.
To unsubscribe from this group, send email to
https://github.com/rails/rails/issues/1322
Does this pull request fix the issue?
https://github.com/rails/rails/pull/1317
No. And I could not reopen the ticket.
Robert Pankoweck
--
You received this message because you are subscribed to the Google Groups Ruby
on Rails: Core group.
To
Any new ideas on this topic ? It seems that we always produce a String
and then turn it into symbol.
Do you want me to create some benchmarks so we can discuss the switch
based on some facts ?
Robert Pankowecki
--
You received this message because you are subscribed to the Google Groups Ruby
Thanks for the information.
I got
NoMethodError: undefined method `-' for #Date:0x97829f0
when trying to subtract two dates so I thought that the operator is
defined in Rails.
Apparently it is not. require 'date' must be called to have it.
Not very intuitive.
Robert Pankowecki
--
You
/6448-i18n-key-collision-with-namespaced-models#ticket-6448-11
I would have:
class Articles
module Articles
class Articles::Articles
This a big break in API and it happens second time during last 5
releases. Could we clarify this thing once for all the time?
Robert Pankowecki
--
You received
I meant
class Articles
module Articles
class Articles::Category
--
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@googlegroups.com.
To unsubscribe from this group, send email to
for RC release and the ability to test and veto :-)
Robert Pankowecki
--
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@googlegroups.com.
To unsubscribe from this group, send email
to create tickets for them ?
Yes please. Does this happen on 3.0.4 too?
Yes 3.0.4, 3.0.5, 3.0.6.rc1, maybe even earlier versions.
https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/6654-dateyesterday-and-datetomorrow-returns-wrong-values
Robert Pankowecki
--
You received
:i18n_key method anymore.
Robert Pankowecki
--
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@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscr
= Wed, 30 Mar 2011
As you can see the simple expectation that yesterday = today -1 and
tomorrow = today + 1 is apparently not true in some cases. This
problem probably happens around midnight in some zones...
Do you want me to create tickets for them ?
Robert Pankowecki
--
You received
scenarios.
Robert Pankowecki
--
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@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscr...@googlegroups.com
it ?
Robert Pankowecki
--
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@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscr...@googlegroups.com
Or db:test:prepare ...
Robert Pankowecki
--
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@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscr
?
Robert Pankowecki
--
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@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscr...@googlegroups.com.
For more
in development environment to an
unsupported value that does not change the behavior at all makes me a
little confused.
Robert Pankowecki
--
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
My guess is that we do now want to test IE using Chrome mode in
development environment because we want to use the application like a
user with normal IE to see possible differences in behavior.
Robert Pankowecki
--
You received this message because you are subscribed to the Google Groups Ruby
...My guess is that we do NOT want ...
--
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@googlegroups.com.
To unsubscribe from this group, send email to
it works the same way in master ?
Robert Pankowecki
--
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@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscr
the intentions clearly
Robert Pankowecki
--
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@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscr
by David ?
Robert Pankowecki
--
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@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscr
and other
nice methods...
If that's possible, maybe that's our goal ?
Robert Pankowecki
--
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@googlegroups.com.
To unsubscribe from this group
are you trying to do it directly?
I think you should use something like http://davmail.sourceforge.net/ as a
proxy.
Next time ask such questions on rails-talk list.
Robert pankowecki
Http://robert.pankowecki.pl
W dniu 2011-01-05 22:39 użytkownik gReg gdjamer...@gmail.com napisał:
Trying
I submited additional patches (master and 3.0-stable) for bug #6036
because it was not fixed completely.
https://github.com/rails/rails/pull/147
https://github.com/rails/rails/pull/148
Robert Pankowecki
--
You received this message because you are subscribed to the Google Groups Ruby
on Rails
I'm glad to hear it.
Robert Pankowecki
--
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-c...@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails-core+unsubscr
Today I noticed that calling object.collection.destroy_all leads to
calling association callbacks like ex. :before_remove but
object.destroy does not call those callbacks when configured
with :dependent = :destroy option.
You can find that hbtm uses collection.clear which under the hoods
calls
but they will stay forever in the application.
I think that version a is better.
I would like to here other opinions.
Robert Pankowecki
--
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-c
,
:activerecord.errors.messages.blank,
:errors.attributes.name.blank,
:errors.messagges.blank,
Can't be blank
]
Both would work.
I would like to know what you think about the problem and solution.
Robert Pankowecki
--
You received this message because you are subscribed to the Google Groups Ruby
, :finalize = true
or
content_for :foo, baz, :freeze = true
Robert Pankowecki
--
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-c...@googlegroups.com.
To unsubscribe from this group, send email
be extended to all of the action_ and active_
components.
Totally agree.
Robert Pankowecki
--
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-c...@googlegroups.com.
To unsubscribe from this group
might want to verify so it is applied faster.
Robert Pankowecki
--
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-c...@googlegroups.com.
To unsubscribe from this group, send email to
rubyonrails
I made a patch for a bug that I found in AR:
https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/5125-collection_singular_ids-method-raises-an-exception-when-primary_key-is-string-rails-3
I'm looking for some people to review it. It is a very simple patch
with tests included.
I
54 matches
Mail list logo
