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. Lookup type that returns results greater than a given value.






2. Defines a many-to-many relationship. You use it just like any other Field type: by including it as a class attribute of your model.






3. If you pickle a QuerySet - this will force all the results to be loaded into memory prior to pickling. When you unpickle a QuerySet - it contains the results at the moment it was pickled - rather than the results that are currently in the database.






4. Use this method to reverse the order in which a queryset's elements are returned. Calling this method a second time restores the ordering back to the normal direction.






5. When to run syncdb






6. 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.






7. Returns a ValuesQuerySet -- a QuerySet that returns dictionaries when used as an iterable - rather than model-instance objects.






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






9. Returns a dictionary of aggregate values (averages - sums - etc) calculated over the QuerySet. Each argument to this method specifies a value that will be included in the dictionary that is returned.






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






11. These are specified as keyword arguments to the QuerySet methods filter() - exclude() and get(). These take the form field__lookuptype=value .






12. Performs an SQL delete query on all rows in the QuerySet. This method is applied instantly. You cannot call this method on a QuerySet that has had a slice taken or can otherwise no longer be filtered.






13. Lookup type that returns results with a case-sensitive start sequence.






14. These are "anything that's not a field" - such as ordering options (ordering) - database table name (db_table) - or human-readable singular and plural names (verbose_name and verbose_name_plural)






15. Takes the ouput of one filter and uses it as input for another filter. This works because a refinement of a QuerySet is itself a QuerySet.






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






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






18. 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






19. Lookup type that yields an "exact" match. If you don't provide a lookup type -- that is - if your keyword argument doesn't contain a double underscore -- the lookup type is assumed to be of this sort.






20. If True - the table does not permit duplicate values for this field.






21. 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






22. A convenience method for constructing an object and saving it all in one step.






23. Returns True if the QuerySet contains any results - and False if not. This tries to perform the query in the simplest and fastest way possible - but it does execute nearly the same query. This means that calling this method on a queryset is faster th






24. 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.






25. 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






26. Returns the object matching the given lookup parameters






27. Lookup type for date/datetime fields that finds an exact month match. Takes an integer 1 (January) through 12






28. 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.






29. 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.






30. Returns a new QuerySet that uses SELECT DISTINCT in its SQL query. This eliminates duplicate rows from the query results.






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






32. A Q object that encapsulates queries for entries with a question value that starts with 'What' in a case-insensitive fashion.

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


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






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






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






36. If this option is True - the field is allowed to be blank. Default is False.






37. Defines a many-to-one relationship. ou use it just like any other Field type: by including it as a class attribute of your model.






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






39. The first element in this iterable is the value that will be stored in the database - the second element will be displayed by the admin interface - or in a ModelChoiceField.






40. Takes a list of primary-key values and returns a dictionary mapping each primary-key value to an instance of the object with the given ID.






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






42. By default - results returned by a QuerySet are ordered by the ordering tuple given by the ordering option in the model's Meta. You can override this on a per-QuerySet basis by using the this method.






43. A Manager method that returns a new QuerySet containing objects that match the given lookup parameters.






44. A convenience method for looking up an object with the given kwargs - creating one if necessary.






45. This field is added automatically - but this behavior can be overridden






46. 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






47. A QuerySet is iterable - and it executes its database query the first time you iterate over it.






48. Operator for comparing two model instances for equality. Behind the scenes - it compares the primary key values of two models.






49. If this option is True - Django will store empty values as NULL in the database. Default is False.






50. Fields are specified by these






Can you answer 50 questions in 15 minutes?



Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests