Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 943091
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 15, 20262026-05-15T22:22:50+00:00 2026-05-15T22:22:50+00:00

First I was using this request: Model.object.get(name=’something’, date=somedatavariable) But then I needed to extend

  • 0

First I was using this request:

Model.object.get(name='something', date=somedatavariable)

But then I needed to extend my query and change it to this:

Model.objects.get(name__icontains="something", date__range(start_date,end_date))

Suddenly my database takes 5 times longer than with the original query. What’s going on here, and how can I make it faster?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-15T22:22:51+00:00Added an answer on May 15, 2026 at 10:22 pm

    A case-insensitive wildcard search (name__icontains='something') will DEFINITELY be a more expensive DB query than a case-sensitive exact match (name='something'). 5 times slower doesn’t sound unreasonable, and it will vary heavily based on any and all of the following:

    • Database Engine (MySQL, PostgreSQL, SQLite, etc.)
    • Number of records in the DB
    • Volume of text in each name field that it has to search through
    • Whether or not there’s an appropriate index the DB can use for that column

    The last one there is very tricky. Doing full-text indexing for a database is very hard to get right, very easy to get wrong, and not even supported by all database engines.

    The same goes for date vs. date__range: you’re using a quick, simple, easy-to-index exact match in one, and an inexact match in the other.

    The bottom line: if you don’t need inexact matches, then don’t use them. They’re expensive DB operations and WILL take significantly longer.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.