innodb ibdata1 file grows irreversibly from testing

from what I understand, the ibdata1 file doesn't recover space from dropped tables. Since django testing creates a test database and then drops it, repeatedly, does this contribute to the ibdata1 file size? Thanks Cody -- You received this message because you are subscribed to the Google Group

Re: Unit Testing: temporarily altering django settings

nt environment (with different settings) for each app? Is there another way to fool a testcase into thinking that an app has not been installed? Thanks again, Cody On Feb 17, 2:00 pm, Phlip wrote: > On Feb 17, 12:03 pm, Cody Django wrote: > > > For example, I have a captcha that

Unit Testing: temporarily altering django settings

For example, I have a captcha that is used in parts of a site that affects form logic. The django settings has a variable CAPTCHA = True, which acts as a switch. I'd like to change this setting in the setup for each TestCase. The regular unittests tests (in which we are assuming the captcha is of

Re: adding user instance to the comments constructor for a dynamic comment form

sure, whatever. maybe you miss the point: I'd like to include the user instance in the constructor. Is there a way to do this without rewriting the comments framework? C On Aug 29, 4:24 pm, "Evan H. Carmi" wrote: > On Sun, 29 Aug 2010 16:08:45 -0700 (PDT) > > Cod

adding user instance to the comments constructor for a dynamic comment form

I'd like to have the comment form contain a captcha if the user is logged in. short of rewriting the provided comment template tags I haven't found a solution. I'm curious if this issue hasn't been already addressed. Thanks -- You received this message because you are subscribed to the Google

creating formset with unknown number of unique forms

the formset will contain an unknown series of questions. Each question contains a unique prompt, integerfield for the value, and a choicefield with a unique list of items, based on the scope of the question. I would like to use a formset so I can iterate over each question in the template, markin

Re: Help a newbie with his simple foreignkey problem?

Sorry - it should read: b = Book.objects.get(id=1) #new book request.user.get_profile().shelf1.add(b) #add book to shelf1 request.user.get_profile().shelf1.remove(b)#remove from shelf1 request.user.get_profile().shelf2.add(b) #add to shelf2 I th

Help a newbie with his simple foreignkey problem?

Hi - I'm having a hard time wrapping my head around one-to-many relations. I'd like to be able to do this in a view: b = Book.objects.get(id=1) #new book request.user.get_profile().shelf1.add(b) #add book to shelf1 request.user.shelf1.remove(b) #remove from shelf1 request.user.shelf2.add(b)

Re: Weird: the path to the image, retrieved using filebrowser, is rewritten with a wrong relative instead of absolute.

sorry -- already a fix: http://code.google.com/p/django-tinymce/issues/detail?id=22&can=1&q=image&colspec=ID%20Type%20Status%20Priority%20Milestone%20Reporter%20Owner%20Summary On Aug 17, 7:31 pm, Cody Django wrote: > I really don't know what is going on here.  I've

Weird: the path to the image, retrieved using filebrowser, is rewritten with a wrong relative instead of absolute.

I really don't know what is going on here. I've checked all my settings for django-filebrowser and django-tinymce. 1) Using tinymce in admin, I'll click on "add image" 2) Click on "filebrowser" icon in the image-prompt window, which opens the filebrowser window 3) Click on an image, which opens

upgraded to python2.5, but error-reports/traceback still references python2.3?

This is weird: I used to use python2.3 on the mediatemple server, but recently upgraded to python2.5. I've also installed mysqldb, pil, ect under python2.5. I've updated my pythonpath so the python2.5 route is being used. Everything works just fine, but I've noticed in the traceback that python

Re: python 2.5 --> 2.3, now imagefield error

yes, and it contains the jpg and gif plugins, which I assume means that it does support jpgs. On Jul 27, 9:15 pm, Darryl Ross wrote: > Cody Django wrote: > > ImageFields worked just fine until I moved to a new server. Now I get > > error messages "Upload a valid image"

Re: python 2.5 --> 2.3, now imagefield error

checked: - pil supports jpgs - permissions set to 775 on upload folders On Jul 27, 7:44 pm, Cody Django wrote: > All imagefields give this error: Upload a valid image. The file you > uploaded was either not an image or a corrupted image. > > I suspect that imagefield itself is com

python 2.5 --> 2.3, now imagefield error

All imagefields give this error: Upload a valid image. The file you uploaded was either not an image or a corrupted image. I suspect that imagefield itself is compatible with python 2.3, so where else could the problem be? It's not with the image. Ideas are greatly appreciated... Thanks. --~--

python 2.5 --> 2.3, now imagefield error

ImageFields worked just fine until I moved to a new server. Now I get error messages "Upload a valid image". I know the images are fine, the media root and www_url are correct, so what else could this be? Ideas are greatly appreciated! Cody --~--~-~--~~~---~--~~