I have found that, using the mysql-ruby gem leads to 40 MB more memory
consumption in my tests than plain mysql.rb.
Is anyone aware of this?
My test loads a nasty grid of values using many include statements
which result in about 5000 rows being returned (the actual number of
rows is much less b
Hey guys,
Thanks to everyone who's contacted us about helping out with some
systems administrator work. We got a few more replies than expected
and will get back to you guys soon once we have an idea of how to go
forward / pick someone.
If you're interested in helping out, just let me know.
-
> Jeremy has been contributing patches since March '06, and won (#1) the
> original CDBaby Hackfest.
We got Jeremy working closely with Marcel on documentation now, so I
think we have that angle covered. But we're still looking to get a few
more code contributors into code as well.
--~--~--
> I have been looking at ActiveRecord's serialization code, and noticed
> that ActiveRecord::XmlSerializer#serializable_attributes purposely
> excludes the STI inheritance column per ``options[:except] =
> Array(options[:except]) | Array(@record.class.inheritance_column).''
> Is there a particular
Ok, here's more info about Jeremy:
Jeremy has been contributing patches since March '06, and won (#1) the
original CDBaby Hackfest.
He's still the #6 contributor for 2007.
He worked on the Rails Documentation Project, rewrote all of the
documentation for ActiveResource and ActionView (see patches
Hey,
I have been looking at ActiveRecord's serialization code, and noticed
that ActiveRecord::XmlSerializer#serializable_attributes purposely
excludes the STI inheritance column per ``options[:except] =
Array(options[:except]) | Array(@record.class.inheritance_column).''
Is there a particular rea
I'd be more than happy to volunteer for this, at least it would be
something I'd be a lot more capable of doing since I currently work as
a sysadmin at a rails hosting company (http://www.brightbox.co.uk).
Scott
On Nov 6, 5:14 pm, DHH <[EMAIL PROTECTED]> wrote:
> > So who should update the offic
On Mon, 5 Nov 2007 06:35:42 -0700, Chad Woolley wrote:
> On 11/5/07, Hongli Lai <[EMAIL PROTECTED]> wrote:
>> The syntax is too obscure and not many people know it. It could
>> confuse people who use Rails for the first time, or people who are not
>> intimately familiar with YAML. I think it's mo
Once again, sorry for the delay. We didn't drop the ball and are still
working on a proposal. We have one more meeting scheduled for
tomorrow. Things look quite good and since we came to a consensus, I
believe we should be done soon.
We'll keep you posted.
- Matt
On Oct 24, 1:12 pm, "Matt Aimo
DHH wrote:
> Your team can probably just inline patch that if they're on a recent
> enough version of rails.
Done, and working.
Many thanks.
-- hugh
--
Posted via http://www.ruby-forum.com/.
--~--~-~--~~~---~--~~
You received this message because you are su
I totally disagree with the "perlism" comparison here. If it is a
taste thing, that's understandable, but saying the above code snippet
is too hard to read or akin to perlism, I don't agree. But whatever
the consensus is, is cool with me.
On Nov 7, 6:15 am, Hongli Lai <[EMAIL PROTECTED]> wrote:
>
> From my reading ofhttp://dev.rubyonrails.org/ticket/9975it seems like
> this may be fixed, with the correct UTF encoding? If so, should it be
> simple for the dev team building the RoR RAPI I'm accessing to apply the
> patch?
This has been fixed. Here's the change that actually does the work:
> Could I beg a quick review and, if worthy, a few +1s to get this into
> Rails 2?
Good stuff. Applied.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email
DHH wrote:
> This has been fixed. Here's the change that actually does the work:
>
Outstanding- thanks for letting us know.
- D
--
Posted via http://www.ruby-forum.com/.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Gro
I rarely use the same username and password for my production and
development databases, so not only does this obfuscate the file a
little bit it also makes me have to do more work when I get ready to
do production testing and deployment.
--Jeremy
On Nov 4, 2007 2:32 PM, Robert Evans <[EMAIL PRO
Agree. Too much DRY leads to perlism sometimes, this is quite close to
that. And not much to gain from it either.
On 11/7/07, Hongli Lai <[EMAIL PROTECTED]> wrote:
>
> On Nov 6, 3:52 pm, revans <[EMAIL PROTECTED]> wrote:
> > How about keeping the structure I suggested, but adding comments
> > exp
On Nov 6, 3:52 pm, revans <[EMAIL PROTECTED]> wrote:
> How about keeping the structure I suggested, but adding comments
> explaining the structure for clarification? To me it makes sense
> because it DRY's up your code, something Rails advocates, but doesn't
> follow in this area.
Yes but Rails a
17 matches
Mail list logo
