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






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






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






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






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






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






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






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






9. Lookup type that returns results with a case-insensitive end sequence.






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






11. Lookup type for date/datetime fields that finds an exact day match.






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






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






14. Adds to each object in the QuerySet with the provided list of aggregate values (averages - sums - etc) that have been computed over the objects that are related to the objects in the QuerySet. Each argument to this is content that will be added to ea






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






16. restrictions on ________: (1) Your intermediate model must contain one - and only one - foreign key to the target model. (2) Your intermediate model must contain one - and only one - foreign key to the source model. (3) When defining a many-to-many r






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






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






19. This query uses an F object to increment the pingback count for every entry in the blog.

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


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






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






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






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






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






26. To activate your models






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






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






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






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






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






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






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






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






35. (1) These cannot be Python reserved words - because that would result in a Python syntax error. (2) These cannot contain more than one underscore in a row - due to the way Django's query lookup syntax works.






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






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






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






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






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






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






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. Lookup type that returns results with a case-sensitive end sequence.






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






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






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






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






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






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






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







Sorry!:) No result found.

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