hello kanniga,
I use correct user and password.
I can get data from database.
I read about it in an one post that described what may be due not
correct settings of connect to database, but there were no details.
On Jun 5, 2:54 pm, kanniga sivasubramanian
wrote:
> hello yakovenko sir,
> I
hello yakovenko sir,
I think your databse_user and database_password are incorrect.
I had affected by this problem. You will give correct username and
password of mysql.
On Sat, Jun 5, 2010 at 1:02 AM, tmitchell wrote:
> Holy reading comprehension, Batman. Just saw you have DEBUG off,
>
Holy reading comprehension, Batman. Just saw you have DEBUG off,
ignore previous comment.
On Jun 4, 10:34 am, Кирилл Яковенко
wrote:
> I have tried this method, but it didn't give any results.
> I suspect that this is due to incorrect settings of the database or connect
> to it.
>
> 2010/6/4 Dj
Are you running with DEBUG on? I've noticed the same memory growth in
standalone scripts when in DEBUG mode.
It may be related to this:
http://docs.djangoproject.com/en/dev/ref/templates/api/#django-core-context-processors-debug
On Jun 4, 10:34 am, Кирилл Яковенко
wrote:
> I have tried this met
I have tried this method, but it didn't give any results.
I suspect that this is due to incorrect settings of the database or connect
to it.
2010/6/4 Dj Gilcrease
> On Fri, Jun 4, 2010 at 6:44 AM, yakovenko wrote:
> > import os
> > import sys
> > os.environ['DJANGO_SETTINGS_MODULE'] = 'md.setti
On Fri, Jun 4, 2010 at 6:44 AM, yakovenko wrote:
> import os
> import sys
> os.environ['DJANGO_SETTINGS_MODULE'] = 'md.settings'
> sys.path.append('/md/lib')
> from django.db import close_connection, reset_queries
> from md.mddata.models import Info
> def test():
> for i in Info.objects.all():
>
Hello guys,
I use django ORM in standalone daemon. And It sucks more and more
memory.
I have created small script for testing:
---
import os
import sys
os.environ['DJANGO_SETTINGS_MODULE'] = 'md.settings'
sys.path.append('/md/lib')
from django.db
On Sat, 2009-02-07 at 19:27 -0800, python6009 wrote:
> Hi,
>
> I am using matplotlib/pyplot on my site to dynamically generate PNG
> plots. And I am experiencing dramatic memory leaks. Within 10-15
> hits, my Apache process grows from 15-20M to 100M.
Let's be accurate with
On Sat, Feb 7, 2009 at 10:27 PM, python6009 wrote:
>
> Hi,
>
> I am using matplotlib/pyplot on my site to dynamically generate PNG
> plots. And I am experiencing dramatic memory leaks. Within 10-15
> hits, my Apache process grows from 15-20M to 100M.
>
> I am using Dj
Hi,
I am using matplotlib/pyplot on my site to dynamically generate PNG
plots. And I am experiencing dramatic memory leaks. Within 10-15
hits, my Apache process grows from 15-20M to 100M.
I am using Django 1.0.2-final, Apache 2.2.1, Python 2.4.3, matplotlib
0.98.5.2. The leak happens under
ject line and the mention about running out of memory in the
original post caused a knee-jerk "Yikes!" reaction for me, based on
my all-too-real experiences with memory leaks.
I'll try to take a deep breath and relax the next time I see "memory
leak" in a Django threa
s wrong in this particular scenario.. but all I have
to say is....
Memory leaks should be taken very seriously and should be hunted down
and exterminated with extreme prejudice.
ink to that I'm relatively smart guy, but tracking down memory leaks
in Python truly humbles me.
-Jason
On 2/7/06, Jason Huggins <[EMAIL PROTECTED]> wrote:
Yes, Python has built-in garbage collection, but is way to easy tocreate circular references between objects (parent references child,child references parent)... Once that circular reference is createdbetween two objects, the objects will never be
I don't know what is wrong in this particular scenario.. but all I have
to say is....
Memory leaks should be taken very seriously and should be hunted down
and exterminated with extreme prejudice.
Yes, Python has built-in garbage collection, but is way to easy to
create circular refer
Your setting might be using DEBUG = True, which save all SQL queries and
its start/stop time for debugging when something goes wrong. Try turning
it to False.
[EMAIL PROTECTED] wrote:
Hi all
I am wondering if other people have noticed an apparent bug in Django
when using the DB API to inser
Hi all
I am wondering if other people have noticed an apparent bug in Django
when using the DB API to insert a large number (~1 million) of records
(each record ~2k) into MySQL (WinXP/Python 2.3).
Here is a simplified/clean version of the code I am running:
from django.models.appname import foos
17 matches
Mail list logo
