Hi all, I was in two minds about writing this as a ticket, mainly because I understand that it is something that is a design decision.
Okay so the issue I came across today was that one of my python developers changed some syntax on one of my views with loads some data from the database, this particular model was being filtered, and limited. However due to the fact that the limit syntax was using pythons slicing syntax, and not a limit method, he thought that it wouldn't affect db (I have since showed him that the table in question has 3 million+ rows, and that grows by a few thousand every night). However it does raise and interesting point - should the limit syntax be apart of a method, rather than hijack the python syntax, is it too magic? I'm very open to opinions here, as it is both clearly labeled in the Documentation and has stuck so long, but it was an interesting development for a python developer to come into Django for the first time and discover this. Regards, Mike Scott --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
