Re: operationalError 2002, mysql on osx 10.9

2007-05-02 Thread Mark Phillips
On May 2, 2007, at 12:26 PM, Michael K wrote: > > On May 2, 3:25 pm, Michael K <[EMAIL PROTECTED]> wrote: >> >> Try setting DATABASE_HOST to 'localhost' instead of blank. What OS >> are you running this on? > > This will teach me to read the subject closely. I should have went > with my gut fee

Re: operationalError 2002, mysql on osx 10.9

2007-05-02 Thread Mark Phillips
On May 2, 2007, at 12:25 PM, Michael K wrote: > > On May 2, 10:09 am, Mark Phillips <[EMAIL PROTECTED]> wrote: >> Being a newbie has its challenges... > > I know exactly what you mean. > >> The server is running mysql, I use phpMyAdmin and a couple of other >> applications successfully with it. >

Re: operationalError 2002, mysql on osx 10.9

2007-05-02 Thread Michael K
On May 2, 3:25 pm, Michael K <[EMAIL PROTECTED]> wrote: > > Try setting DATABASE_HOST to 'localhost' instead of blank. What OS > are you running this on? This will teach me to read the subject closely. I should have went with my gut feeling that it was Mac OS X :) Michael --~--~-~--

Re: operationalError 2002, mysql on osx 10.9

2007-05-02 Thread Michael K
On May 2, 10:09 am, Mark Phillips <[EMAIL PROTECTED]> wrote: > Being a newbie has its challenges... I know exactly what you mean. > The server is running mysql, I use phpMyAdmin and a couple of other > applications successfully with it. > There is an existing database of the same name as the new

operationalError 2002, mysql on osx 10.9

2007-05-02 Thread Mark Phillips
Being a newbie has its challenges... Before going any further on the answers to my earlier post, I thought I should walk through the setup process once more. I set up a new app. I can load the "it worked!" page using a browser on the localhost with "runserver". When I ran the "manage.py sync