On Saturday, April 17, 2010 06:04:58 pm John Karr wrote:
In my own analysis the Time and Effort to learn DBIx is greater than the
Time wasted writing repetitious DBI code, the time I've already invested
on DBIx has shown that there is a better way than DBI, but for me it isn't
DBIx.
In my own
On Sunday, April 18, 2010 12:14:55 am Eden Cardim wrote:
On Sat, Apr 17, 2010 at 8:04 PM, John Karr brain...@brainbuz.org wrote:
Both Fey and SQLDB are a nativist approach to SQL (much like TT is to
html)
TT isn't a native approach to html, by far. In fact, it has quite a
few things going
I have a cron job that watches for changes to SVN, and when found the cron
script exports the code and runs the tests. The idea is to notify
developers if they check in code that causes testing to fail.
I'd like to move away from using my custom scripts to a more generic tool
that will do
On Sun, Apr 18, 2010 at 11:22 AM, Bill Moseley mose...@hank.org wrote:
I have a cron job that watches for changes to SVN, and when found the cron
script exports the code and runs the tests. The idea is to notify
developers if they check in code that causes testing to fail.
I'd like to move
On 16 Apr 2010, at 04:49, Ashley wrote:
It's a longshot that this is relevant to the problem but it is
relevant to Engine::CGI and I needed an excuse to bring it up again.
There is a long-standing bug in the prepare_path of
Catalyst::Engine::CGI that wrecks certain kinds of apache path
On 16 Apr 2010, at 01:53, Jason McIntosh wrote:
Howdy y'all,
Since upgrading to Catalyst 5.8022 on Wednesday, I've found that no
Catalyst requests coming from Apache server-side includes work.
If the user requests foo.shtml, and that file contains !--#include
virtual=/catalyst/header --,
On 18 Apr 2010, at 16:22, Bill Moseley wrote:
Do you do anything similar? Anyone using Smolder and/or
SmokeRunner::Multi or other standard tools for their in-house code?
At work, we're using hudson, and Tap::Harness::JUnit.
It's entirely a dog and uses a million RAM, but does work quite
On Sun, Apr 18, 2010 at 7:19 PM, Tomas Doran bobtf...@bobtfish.net wrote:
Yes, this is due to the change in 5.80015:
...and rolling my installed version back to 5.80014 does indeed make
my problem go away. (As you suggested it would, over on #catalyst a
couple of days ago.)
Thanks again for
