About Kent Cowgill
Articles filed under...
abs ab_ripper andylester arms back baggyshorts bestpractices biceps bike birthday blog bugs bus calculator cardio catalyst cgi chart chest chinups code cpan datamodel dbi doctor documentation exercise exhaustion fitness flattire flat_tire google gps heart_rate helmet history home houston html humor journal kate kenpo kenpo_x kettlebell knees lazy legs lisa lisanne maps math matthew michaelmckenna mom montreal motivation movie mysql oops orm P90X pain park patellar_tendonitis patrick pdf perl phb photos physical_therapy plyometrics poor_gait presentation procrastination progress pullups pushups pyramid rabbits racecondition rant refactor rest ribs ride route running shoulders situps slides sore spike sql statistics syntax test testing textile timex training triceps ups versioncontrol video vim vimrc walk warren work workouts yapc yapcna2007 yoga youtube

A R C H I V E S

(3)
(1)
(3)
(2)
(7)
(15)
(16)
(25)
(3)
(4)
(2)
(4)
(11)
(1)
(1)
(3)
(2)
(2)
(10)
(5)
(2)
(3)
(4)
(9)
(21)
(3)
(3)
(1)
(6)
(4)
(1)
(4)
(3)
(2)
(1)


    Is Kent Cowgill Online?
    View Kent Cowgill's profile on LinkedIn
    Add to Technorati Favorites

    Recent Entries...

    Re: Re: Yoga kicks my butt

    Chris @ 46: Tatyana @ 21 – at best its a stop gap measure...

    Re: Vibram FiveFingers FTW

    Hats off to whoever wrote this up and potesd it....

    Re: A little more detail on using a new model

    百度 [url=http://www.sina.com]sina[/url] ...

    Re: Catching up through week 7

    testing video ...

    Re: Porting a non-Moose object to Moose

    Wow, look what I found, greedy genius ...

    Re: Porting a non-Moose object to Moose

    Kevin, You're right, that does seem a little confusing. ...

    Re: Porting a non-Moose object to Moose

    Wait. I'm confused. Moose isn't the tool to reach for. So...

    Re: Porting a non-Moose object to Moose

    You should switch to MooseX::Types to declare your Typed and...

    Porting a non-Moose object to Moose

    I'm currently working with a lot of legacy code in an envi...

    Testing strategy for mocking code

    I keep finding myself using the following idiom for writing ...

    A little more detail on using a new model

    kent Cowgill

    The first time around, I was using a flat(ish) SQLite file, which worked just fine from my development platform, i.e. running the server as myself, connecting to it on port 3000.

    All well and good, but once I moved the application over to running under mod_perl, I kept getting errors like "Can't open readonly file" "Can't open any file" etc. I was sure it was permissions, so I chown'd the database file to nobody, and iteratively worked up to chmod'ing it to 777 - even moved it to a more publicly accessible location.

    I still don't know what it was. Instead, I moved my database schema over to a mysql database, regenerated my Model modules with the helper script, changed the Model module's references (before I refered to the Model module as blog::Model::CDBI::Blog, but I had to change that to blog::Model::CDBI::mysql::Blog in two places in my Controller - but other than that, *every*thing else worked flawlessly, including the ability to add new posts :-)

    Re: A little more detail on using a new model

    Tory Burch Travel Wallet

    百度
    [url=http://www.sina.com]sina[/url]

    Related Photos: None

    Main Page | Login

    Do you want to buy me ? Find more gift ideas at my wishlist