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. Returns a new QuerySet that uses SELECT DISTINCT in its SQL query. This eliminates duplicate rows from the query results.






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






3. Lookup type for date/datetime fields that finds a 'day of the week' match.






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. Exception raised by get(**kwargs) if more than one item matches the query.






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






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






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






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






10. Lookup type that returns results with a case-insensitive start sequence.






11. This gives your model metadata.






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






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






14. Evaluates the QuerySet (by performing the query) and returns an iterator over the results. A QuerySet typically caches its results internally so that repeated evaluations do not result in additional queries; this method will instead read results dire






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






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






17. Lookup type that takes either True or False and corresponds to SQL queries of IS NULL and IS NOT NULL - respectively.






18. Manager method used to retrieve every object in a model.






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






20. what the field _______ determines: (1) The database column type (e.g. INTEGER - VARCHAR); (2) The widget to use in Django's admin interface - if you care to use it (e.g. <input type="text"> - <select>); (3) The minimal validation requirements - used






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






22. Lookup type that yields a case-insensitive match.






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






24. The database that will be used if this query is executed now






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






26. These add custom "row-level" functionality to your objects. These act on a particular model instance.






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. a QuerySet can be sliced - using Python's array-slicing syntax.






29. Sometimes - the Django query syntax by itself can't easily express a complex WHERE clause. For these edge cases - Django provides this QuerySet modifier -- a hook for injecting specific clauses into the SQL generated by a QuerySet.






30. Exception raised by get(**kwargs) if no items match the query.






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






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






33. Lookup type that returns results less than or equal to a given value.






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






35. To activate your models






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






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






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






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






40. Negation operator for Q objects.






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






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






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






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






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






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






47. The value given in the absence of a specified value for the field. This can be a value or a callable object. If callable it will be called every time a new object is created.






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






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






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