Hi Michael,
I want to report a bug:
The latest activerecord-oracle-adapter-1.0.0.9250.gem has a dependency
problem: when launch the webrick server of a Rails 2.0 project with froze
Rails 2.1, error ocurrs:
> $ ruby script/server
> => Booting Mongrel (use 'script/server webrick' to force WEBrick
> I agree that the internal variables should have ugly underscored
> names. The problem is that it's not exactly trivial to replace
> everything in a way that doesn't trash someone else's existing app or
> plugin. I'd suggest starting a git branch started and having folks
> run it against their
On 7/6/08, Bryan Liles <[EMAIL PROTECTED]> wrote:
>
>
> On Jul 6, 2008, at 3:51 AM, tonypm wrote:
>
> > I have been bitten by errors, and template name clashes and the like,
> > but coming up with an extended name in the app is usually fairly
> > trivial.
> >
>
>
> This is where I take issue.
On Fri, Jul 4, 2008 at 10:39 PM, zilkey <[EMAIL PROTECTED]> wrote:
>
> I think loading the environment with db:create and db:drop is
> unnecessary. I've run into scenarios where a plugin does some
> initialization based on the database and raises exceptions if there is
> no database (ultrasphinx
On Jul 6, 2008, at 3:51 AM, tonypm wrote:
> I have been bitten by errors, and template name clashes and the like,
> but coming up with an extended name in the app is usually fairly
> trivial.
>
This is where I take issue. Coding around the framework feels weird.
> After all, you are going to
Whilst the point is entirely valid, IMHO there is equally a sense of
'polluting' the code with loads of __ stuff. The thing I really like
about ruby and rails is the nice readability factor.
I have been bitten by errors, and template name clashes and the like,
but coming up with an extended nam
