Hi all,
Just wondering if you guys think hstore extension should be created
automatically by rails? I see that in ActiveRecord's Rakefile it's been
updated for testing (
https://github.com/rails/rails/blob/master/activerecord/Rakefile#L124-131),
but this doesn't seem to be right for every
Hi all,
I realize this behavior is by design, and in some respects the right thing
to do. It also pre-dates the addition of Enumerable#count. I'm wondering,
however, if it's possible/desirable to allow the caller to access the
Enumerable versions under certain conditions. I originally wrote
I don't think it should be added by default. Not every application will use
it.
On Jan 31, 2013 8:12 PM, kenips ken...@pushpulllabs.com wrote:
Hi all,
Just wondering if you guys think hstore extension should be created
automatically by rails? I see that in ActiveRecord's Rakefile it's been
yeah, -1 by default, but +1 for a patch that would allow me to do it without
having to switch to structure.sql :)
On Thursday, January 31, 2013 at 5:42 PM, Rafael Mendonça França wrote:
I don't think it should be added by default. Not every application will use
it.
On Jan 31, 2013 8:12 PM,
It is already implemented Prem. See the last commits from Aaron.
On Jan 31, 2013 8:45 PM, Prem Sichanugrist sikand...@gmail.com wrote:
yeah, -1 by default, but +1 for a patch that would allow me to do it
without having to switch to structure.sql :)
On Thursday, January 31, 2013 at 5:42 PM,
Possibly activesupport could monkey-patch unsafe Ruby methods like YAML.loadto
be safe by default. The old version could be exposed with a prefix of
unsafe_ (like YAML.unsafe_load).
Like this gem: https://github.com/dtao/safe_yaml.
--
You received this message because you are subscribed to
