Thanks Eric, using a constant wouldn't really benefit me. I was just kinda curious as that's what I originally tried using, and while it worked I was kinda thinking to myself that "this probably isn't a good thing."
I'll probably end up using ActiveRecord. I just get caught up sometimes in the memory game, and hate seeing my memory usage sky rocket as I pull large results. But if I have the memory, why not use it to my advantage! James On 1/26/07, Eric Mill <[EMAIL PROTECTED]> wrote: > Maybe, but does that benefit you? Constants aren't allowed to be set > more than once (when you first define them), so using one as a DB > connection might potentially cause problems if you ever reset it. > It's also "unfashionable" in Ruby land to use constants over instance > variables for this work. > > -- Eric _______________________________________________ Camping-list mailing list [email protected] http://rubyforge.org/mailman/listinfo/camping-list
