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 in a given list.






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






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






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






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






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






7. Fields are specified by these






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






9. Lookup type for date/datetime fields that finds an exact year match. Takes a four-digit year.






10. Lookup type that finds a case-insensitive regular expression match.






11. Lookup type that returns results greater than a given value.






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






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






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






15. This method returns tuples of values when iterated over. Each tuple contains the value from the respective field passed into the call to this method -- so the first item is the first field - etc.






16. When to run syncdb






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






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






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






20. To activate your models






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






22. These methods are intended to do "table-wide" things.






23. This object allows you to compare the value of a model field with another field on the same model. Django supports the use of addition - subtraction - multiplication - division and modulo arithmetic with these objects - both with constants and with o






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






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






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






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






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






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






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






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






32. This gives your model metadata.






33. Evaluation happens upon use the "step" parameter of slice syntax - the first time you iterate over it - when pickling or caching results - upon calling repr() - upon calling len() - upon calling list() - upon calling bool()






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






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






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






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. Negation operator for Q objects.






39. Defined by django.db.models.ForeignKey. You use it just like any other Field type: by including it as a class attribute of your model.






40. Disjunction operator for Q objects.






41. Here - you can't use add - create - or assignment (i.e. - beatles.members = [...]) to create relationships. You need to specify all the detail for the relationship required by the intermediate model.






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






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






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






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






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






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






48. Lookup type that tests for inclusion in a case-sensitive fashion.






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






50. Used to get a QuerySet for a model. This is called 'objects' by default.