CollectiveAccess
1.8

Introduction

  • What is CollectiveAccess?

Providence

  • User guide
    • Setup & Install
    • Data Modelling
    • Configuration
    • Search & Browse
      • Overview
      • Search Syntax
      • Search Forms
      • Search Builder
      • Browse
      • Indexing Options
      • Search Engines
        • SQL Search
        • ElasticSearch
      • QuickSearch
      • Basic Search
    • Editing
    • Media
    • Reporting
    • Workflow
    • Import
    • Export
    • Administration
    • Reference
  • Developer guide

Pawtucket

  • User guide
  • Developer guide
CollectiveAccess
  • Docs »
  • Providence user guide »
  • Search & Browse »
  • Search Engines »
  • SQL Search

SQL Search¶

SQLSearch is an engine that employs regular MySQL tables to create an inverted index stored. This technique was used in the 0.5x version of CollectiveAccess and provided reasonable performance and scalability combined with easy deployment (zero-configuration is required). For version 0.6 and 1.0 alternative engines were explored that leveraged existing code (eg. PHP Lucene, MySQL FULLTEXT, SOLR, etc.). While ultimately workable, none of the other options combine the deployment and performance characteristics of the inverted index approach.

A new Unicode-friendly “SQL Search” plugin has been implemented, as of version 1.1, as an alternative to PHP Lucene and MySQL Fulltext, the other “easy deploy” options. As of version 1.1, SQL Search is the default search engine option and as of version 1.3 the only supported “easy deploy” option.

Pros: Performance and scalability are generally good; deployment is effortless

Cons: Indexing can be slow; disk space requirements for indices can be large

Status: Implemented

Next Previous

© Copyright 2023, Whirl-i-Gig Last updated on Sep 21 2023.

Built with Sphinx using a theme provided by Read the Docs.