When you started using mysql did you do a fresh manage.py syndb or sqlite
dump > mysql import? If the latter than you almost certainly have incorrect
create statements.
Drop the mysql db and create it using manage.py syncdb. If you need to
import the data from the existing sqlite db I suggest
hmmm it seems that anything in the database is not set to auto increment
On Thu, Apr 10, 2014 at 11:04 AM, Adam Teale wrote:
> ok, i just enabled auto increment to the comment id field
>
> Seems to work fine!
>
> Now is there any way that this could have been set automatically from
> django? S
ok, i just enabled auto increment to the comment id field
Seems to work fine!
Now is there any way that this could have been set automatically from
django? So i don't have this issue in the future)
Thanks!
On Thu, Apr 10, 2014 at 9:47 AM, Adam Teale wrote:
> sorry I meant django.contrib.comme
sorry I meant django.contrib.comments - not messages
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this g
Hello Mark, thanks for responding to my question
I'm using the built-in django commenting system - django.contrib.messages
It was fine with the sqlite db
I had done a syncdb and the app was working, but it just seems that now
when I add a comment to something there is this issue.
Do I need to m
You say you imported the database. Did you use syncdb to set up the tables?
It sounds like your comment_id field in MySQL is not set as an
auto-incrementing primary key field. Do you have access to that MySQL
database to check, and or update that field definition?
On Wed, Apr 9, 2014 at 2:42 PM,
Hi Guys
I have been working on a django app that was going well using an sqlite db.
I've moved it over to mysql and imported the database
Everything looks good
But when I try to use the django comment system that was working well on
the sqlite db before I get:
OperationalError at /comments/pos
> You may have query caching turned on.
>
> http://www.mysqlperformanceblog.com/2006/07/27/mysql-query-cache/
Also here (for mysql 5.0):
http://dev.mysql.com/doc/refman/5.0/en/query-cache-configuration.html
--~--~-~--~~~---~--~~
You received this message because y
On Feb 5, 12:36 pm, dan0 wrote:
> Hello,
>
> I am having an issue with my msyqld process responding to a query
> after a moderate period of inactivity. I'll issue a simple query such
> as "Person.objects.filter(name__icontains='Dan')", which would map to
> about 5000 entries in a table of roughly
> I think the effect you are seeing is more of MySQL thing than a Django
> thing, so that is where I'd be looking for a better idea of what the server
> is doing to speed up subsequent queries like this (in fact I think I recall
> reading about it at some point in reading up on MySQL, though I don
Also, you could limit the result set to the number of records you
actually need. 5k seems like an absurdly large result set.
One final thing would be if you could pre-cull the Person data by
narrowing it down to active users or something. The active_user field
(if there is one), could quickly k
I'm sure that the Queryset is being evaluated. There is a significant
amount of post-processing which occur to the Django objects before
they're passed to render_to_response.
I agree, this is almost certainly a MySQL issue rather than a Django
issue. The query isn't using an
On Thu, Feb 5, 2009 at 12:36 PM, dan0 wrote:
>
> Hello,
>
> I am having an issue with my msyqld process responding to a query
> after a moderate period of inactivity. I'll issue a simple query such
> as "Person.objects.filter(name__icontains='Dan')", which would map to
> about 5000 entries in a t
Hello,
I am having an issue with my msyqld process responding to a query
after a moderate period of inactivity. I'll issue a simple query such
as "Person.objects.filter(name__icontains='Dan')", which would map to
about 5000 entries in a table of roughly 200,000 rows, and see the
mysqld process st
Hi, I'm having problems with django and mysql over apache2 on windows
2000 server.
I'm getting errors about connecting to mysql database, I figured out it
is about threading problems. I've searched this problem over the
network and I've found a fix in the tickets intended to solve this. I
have ap
15 matches
Mail list logo
