SQL makes selecting all fields in a table quite trivial via the SELECT * (SELECT ALL) clause. Unfortunately, as soon as you omit a column from the list, the SELECT ALL statement goes out the window. Writing out every every column name can quickly become tedious, especially if you happen to be dealing with tables that contain dozens of columns. What if we could select every column but one - selecting by exclusion rather than inclusion? It can be done. In fact there are a couple of ways to do it - one simple, the other, a bit less so. These will be the focus of today's blog.
Every so often, we need to rebuild indexes in Oracle, because indexes become fragmented over time. This causes their performance - and by extension - that of your database queries, to degrade. Hence, rebuilding indexes every now and again can be quite beneficial. Having said that, indexes should not be rebuilt to often, because it's a resource intensive task. Worse, as an index is being rebuilt, locks will be placed on the index, preventing anyone from accessing it while the rebuilding occurs. Any queries trying to access this index in order to return the required results will be temporarily blocked, until the rebuild is complete.
In today's blog, we'll learn how often to build indexes and how to determine when an index needs to be rebuilt.
The number of images in web applications has been growing steadily in recent years. There is also a need to distinguish between images of different sizes, like thumbnails, web display images, and the like. For example, one application that I recently developed shows news items where each item has a thumbnail and main article image. Another app shows company logos in small and large sizes.
Perhaps you've heard that version 15 of Navicat's flagship product, Navicat Premium, was officially released on November 25th. It comes packed with numerous improvements and features to address all of your database development and administration needs. In addition to over 100 enhancements, Navicat includes several new features to give you more ways that ever to build, manage, and maintain your databases. In the last blog, we explored the Data Visualization feature. Today, we'll be taking a look at other improvements, including Data Transfer, Query Builder, Data Modeler and more!
Welcome to part 3 of this series on full-text indexing and searching in MySQL. In Part 1, we saw how MySQL provides full-text search capability via FULLTEXT indexing along with the three following distinct types of full-text searches:
- Natural Language Full-Text Searches
- Boolean Full-Text searches
- Query expansion searches
In Part 2, I described how to perform Natural Language full-text searches in Navicat for MySQL. Today's blog follows where part 2 left off and covers the next type of full-text searching: Boolean Full-Text searches.
- 2021 (1)
- 2020 (1)
- 2019 (1)
- December (1)
- October (1)
- September (1)
- August (1)
- July (1)
- June (1)
- May (1)
- The Between Operator
- Some SELECT Queries You Must Know
- Diagnose Bottlenecks and/or Deadlocks in MySQL 8 using Navicat Monitor
- How the MySQL 8 Performance Schema Helps Diagnose Query Deadlocks
- How the MySQL 8 Performance Schema Helps Diagnose Query Deadlocks (2)
- How the MySQL 8 Performance Schema Helps Diagnose Query Deadlocks (3)
- April (1)
- March (1)
- February (1)
- January (1)
- 2018 (1)
- 2017 (1)
-
Support
-
About Us
