in reply to Re: To use do or eval
in thread To use do or eval

You won't be able to edit with any of your normal tools, or track changes with CVS, or diff it, or grep it, etc. I know it sounds great before you've tried it, but it really ends up being a problem for most projects that do it.

So provide a file based interface :)

I had to work with code in a database once. It was great for performance (the filesystem on that box performed lousily), and writing check in/out scripts was only an hour or so work.

Juerd # { site => 'juerd.nl', plp_site => 'plp.juerd.nl', do_not_use => 'spamtrap' }

Replies are listed 'Best First'.
Re: Re: Re: To use do or eval
by perrin (Chancellor) on Jun 03, 2003 at 16:49 UTC
    If you got better performance from an RDBMS than from a fileystem, something was set up wrong on that machine. Or it was running an OS with a lame filesystem.

      If you got better performance from an RDBMS than from a fileystem, something was set up wrong on that machine. Or it was running an OS with a lame filesystem.

      Both. It was running Windows (and that is badly set up by definition) and the filesystem in question was samba, which used a linux box that in turn got its data through NFS. I hate seeing such configurations without being allowed to fix it.

      Juerd # { site => 'juerd.nl', plp_site => 'plp.juerd.nl', do_not_use => 'spamtrap' }