Hello

I wrote a test case using mysldb with direct python calls and using
the django model classes to insert various sized binary data into a
blob field. First I changed the value of max_allowed_packets in my.cnf
to prove/disprove that mysqldb/django are using it.  Conclusion they
do use my.cnf and setting it to 1k will always cause the error. So I
set it to 32M and tried loading the large data.
Both the mysqldb direct call and django model class routes fail at
some point between 10M and 25M with the max packet error. Seems like a
bug in mysqldb as the same mysql insert works up to 30M. I'm going to
see if there is a later version to try.

Thanks for the help

Owen

On Jul 4, 4:27 pm, Carl Karsten <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > Thanks Martn and Carl.
>
> > I would really like to avoid having to re design the architecture of
> > the application at this stage (its a case of the requirements changing
> > after roll out), althougth thanks for the comments re serving large
> > data volumes.
> > I have made the adjustments suggested 
> > inhttp://dev.mysql.com/doc/refman/4.1/en/packet-too-large.html
> > prior to making these loading the insert directly into  mysql failed,
> > afterwards it suceeded but the insert through django still fails hence
> > my question - Does django ignore the max_allowed_packet setting in
> > my.cnf?
> > if so how can it be increased so that django uses it?
>
> django uses python's mysqldb module, which uses mysql's client library.
>
> My guess is the my.conf you edited is not the one being used.
>
> I would write a little 5 line .py that just connects and inserts a 5m wad of
> data.  my guess is it will fail.
>
> I tried to track down exactly where the .conf file got read, and ran out of
> time.  But I did see that you can specify it as part of the connection:
>
>     89         read_default_file
>     90           file from which default client values are read
>
> http://mysql-python.svn.sourceforge.net/viewvc/mysql-python/trunk/MyS...
>
> I rushed this post and just psoted what I had so far, so let me know if you 
> need
> more details.
>
> Carl K


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to