On Monday, November 24, 2014 10:05:47 PM UTC+1, Rick van Hattem wrote: > > My goal was simply to move the Django project forward but it seems the > problems I've encountered in the field are too uncommon for most other > developers to care or understand. >
Oh, I can assure you that we care and understand (and you are certainly not the only one with a somewhat big site), but in the end I think the arguments against it as shown by Christophe outweigh what you are proposing. That said, I still fail to see the issue, set a memory limit for your apps (man ulimit) and you get a nice MemoryError when libpq tries to overallocate -- including a nice traceback… Adding security guards for any ill written application is not going to fly (especially if it's not as easy as adding a LIMIT which has it's own problems as pointed out), sorry. Cheers, Florian -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/6fa16884-b69c-494b-b795-f6fa4aa24c14%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
