Test your basic knowledge |

Django Queryset

Subject : it-skills
Instructions:
  • Answer 50 questions in 15 minutes.
  • If you are not ready to take this test, you can study here.
  • Match each statement with the correct term.
  • Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. Specifies the model that will be used to govern the many-to-many relationship. You can then put extra fields on the intermediate model. The intermediate model is associated with the ManyToManyField using this to point to the model that will act as an






2. Negation operator for Q objects.






3. This query updates all the headlines with pub_date in 2007 to read 'Everything is the same'.

Warning: Invalid argument supplied for foreach() in /var/www/html/basicversity.com/show_quiz.php on line 183


4. Fields are specified by these






5. This method is for controlling which database the QuerySet will be evaluated against if you are using more than one database. The only argument this method takes is the alias of a database - as defined in DATABASES.






6. A manager method which returns a single object. If there are no results that match the query - this method will raise a DoesNotExist exception. If more than one item matches this query - the method will raise MultipleObjectsReturned.






7. In this case - an intermediate model can have multiple foreign keys to the source model. Here - two foreign keys to the same model are permitted - but they will be treated as the two (different) sides of the many-to-many relation.






8. Accomplish this by using the field name of related fields across models - separated by double underscores - until you get to the field you want. For example - to get all Entry objects with a Blog whose name is 'Beatles Blog': Entry.objects.filter(blo






9. Lookup type that returns results that fall into an inclusive date range.






10. Returns the most recent object in the table - by date - using the field_name provided as the date field.






11. This sets a field to a particular value for all the objects in a QuerySet. You can only set non-relation fields and ForeignKey fields using this method.






12. Keyword shortcut for looking up an object by primary key.






13. Performs an SQL update query for the specified fields - and returns the number of rows affected. This method is applied instantly and the only restriction on the QuerySet that is updated is that it can only update columns in the model's main table. F






14. This gives your model metadata.






15. An iterable (e.g. - a list or tuple) of 2-tuples to use as options for this field. If this is given - Django's admin will use a select box instead of the standard text field and will limit options to those given.






16. Lookup type that returns results greater than or equal to a given value.






17. Lookup type that finds a case-sensitive regular expression match.






18. This style of inheritanc is useful when you're subclassing an existing model (perhaps something from another application entirely) and want each model to have its own database table. Here - each model in the hierarchy is a model all by itself.






19. This query deletes all Entry objects with a pub_date year of 2005.






20. This class type is useful when you just want to use the parent class to hold information that you don't want to have to type out for each child model. This class isn't going to ever be used in isolation. When it is used as a base class for other mode






21. When to run syncdb






22. Extra text to be displayed under the field on the object's admin form to provide assistance to users. It's useful for documentation even if your object doesn't have an admin form.






23. Returns an integer representing the number of objects in the database matching the QuerySet. This never raises exceptions.






24. This method immediately deletes the object and has no return value.






25. Returns a new QuerySet containing objects that match the given lookup parameters.






26. Defined by a OneToOneField. You use it just like any other Field type: by including it as a class attribute of your model.






27. In some complex data-modeling situations - your models might contain a lot of fields - some of which could contain a lot of data (for example - text fields) - or require expensive processing to convert them to Python objects. If you are using the res






28. Each one of these is a Python class that subclasses django.db.models.Model. Each attribute of one of these represents a database field.






29. To activate your models






30. This is a criterion that narrow down a QuerySet based on given parameters.






31. This represents a collection of objects from your database. It can have zero - one or many filters.






32. Returns the object matching the given lookup parameters






33. The default for this is the name of the child class followed by '_set'.






34. If you are using this attribute on a ForeignKey or ManyToManyField - you must always specify a unique reverse name for the field.






35. Lookup type that returns results with a case-sensitive end sequence.






36. If True - this field is the primary key for the model.






37. This model method is used for updating a ManyToManyField.






38. True if the QuerySet has an order_by() clause or a default ordering on the model. False otherwise.






39. This model type is useful if you only want to modify the Python-level behavior of a model - without changing the models fields in any way. This creates a stand-in for the original model. You can create - delete and update instances of this new model






40. This method is more or less the opposite of defer(). You call it with the fields that should not be deferred when retrieving a model. If you have a model where almost all the fields need to be deferred - using this method to specify the complementary






41. Lookup type that corresponds to a boolean full-text search - taking advantage of full-text indexing. This is like contains but is significantly faster due to full-text indexing.






42. Returns a copy of the current QuerySet (or QuerySet subclass you pass in). This can be useful in some situations where you might want to pass in either a model manager or a QuerySet and do further filtering on the result. You can safely call all() on






43. This query finds all entries between a start date of start_date and an end date of end_date.






44. This query finds all entries with an id greater than 4.






45. This query finds all entries with an id in the list [1 - 3 - 4]






46. Exception raised by get(**kwargs) if more than one item matches the query.






47. Lookup type that returns results less than a given value.






48. This tells Django how to calculate the URL for an object. Django uses this in its admin interface - and any time it needs to figure out a URL for an object.






49. This model method saves a model instance to the database. This method has no return value.






50. Returns an EmptyQuerySet -- a QuerySet that always evaluates to an empty list. This can be used in cases where you know that you should return an empty result set and your caller is expecting a QuerySet object (instead of returning an empty list - fo