On 5-7-2012 15:45, Tom Evans wrote:
> On Thu, Jul 5, 2012 at 1:53 PM, Melvyn Sopacua wrote:
>> On 4-7-2012 21:31, Matthew Piatkowski wrote:
DATABASE_PORT = '3036' # Set to empty string for default.
Not used with sqlite3.
>> Typo that should probably 3306.
>>
>
> I'm sur
WOW ! I forget about date ! Sorry
2012/7/5 Tom Evans :
> On Thu, Jul 5, 2012 at 2:59 PM, Sergiy Khohlov wrote:
>> Could you please connect to mysql from console. Is it OK ?
>>
>> Look like
>> mysql is not started
>> you connect to wrong port
>> connect from network is blocked
>> credentials
On Thu, Jul 5, 2012 at 2:59 PM, Sergiy Khohlov wrote:
> Could you please connect to mysql from console. Is it OK ?
>
> Look like
> mysql is not started
> you connect to wrong port
> connect from network is blocked
> credentials are wrong
>
Seriously? WTF? This is a thread from April 2009, the O
Could you please connect to mysql from console. Is it OK ?
Look like
mysql is not started
you connect to wrong port
connect from network is blocked
credentials are wrong
2012/7/5 Tom Evans :
> On Thu, Jul 5, 2012 at 1:53 PM, Melvyn Sopacua wrote:
>> On 4-7-2012 21:31, Matthew Piatkowski wrote:
On Thu, Jul 5, 2012 at 1:53 PM, Melvyn Sopacua wrote:
> On 4-7-2012 21:31, Matthew Piatkowski wrote:
>>> DATABASE_PORT = '3036' # Set to empty string for default.
>>> Not used with sqlite3.
>>>
> Typo that should probably 3306.
>
I'm sure the guy from 2009 that he is quoting will be g
On 4-7-2012 21:31, Matthew Piatkowski wrote:
>> DATABASE_PORT = '3036' # Set to empty string for default.
>> Not used with sqlite3.
>>
Typo that should probably 3306.
--
Melvyn Sopacua
--
You received this message because you are subscribed to the Google Groups
"Django users" gr
mdsmoke, do yourself a favor. You have exposed your password and the user
name of your db; change your password. Also, best practices for using
databases, is create an administrative login insead of using 'root'. Its
much easier for a nasty malicious person or organisation to guess (root)
tha
> Why have you specified port 3036?
-cause i'm partially retarded, that's all...thanks for your help
Matt
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to d
On Sun, Aug 2, 2009 at 9:16 PM, mdsmoker wrote:
>
> when running python manage.py syncdb I got the following errors...
>
> C:\DJANGO~1\mysite>python manage.py syncdb
> Traceback (most recent call last):
> [snip]
super(Connection, self).__init__(*args, **kwargs2)
> _mysql_exceptions.Operational
when running python manage.py syncdb I got the following errors...
C:\DJANGO~1\mysite>python manage.py syncdb
Traceback (most recent call last):
File "manage.py", line 11, in
execute_manager(settings)
File "c:\django-trunk\django\core\management\__init__.py", line 362,
in execut
e_manage
10 matches
Mail list logo
