What's new in mnoGoSearch Pro Standard 3.2.42.1

Apr 12, 2007
  • Minor indexing performance improvements were done.
  • "Indexer is selecting wrong Content-Type" was fixed.
  • "Clear database limitations do not work: error ORA-01795" was fixed.
  • "-Ewordstat: incorrect unicode sequence" was fixed.
  • "invalid UTF-8 byte sequence detected' when INSERT INTO dictXX" was fixed. This error happened when indexing into PostgreSQL with DBMode=multi. The "intag" column type was changed from TEXT to BYTEA in the tables "dict00".."dictFF".
  • "Indexer crashes with -a -y 'content/type'" was fixed.
  • "DateFactor does not work with DBMode=blob" was fixed.
  • "ORA-01785: maxinum number of expressions in a list is 1000" was fixed.
  • "Cannot run -Ewordstat, ORA-01400: cannot insert NULL" was fixed.

New in mnoGoSearch Pro Standard 3.2.38.1 (Mar 15, 2006)

  • Fetching of a list of indexer targets is now much faster with big MySQL databases. The SQL query for target look up was rewritten to creating a temporary table and its further use in a join with the "url" table. It allowed to get rid of a filesort with a huge amount of data. Also, a key using free columns (next_index_time,seed,rec_id) was added for the "url" table, to allow index read instead of full table scan.
  • MinCoordFactor improvements were made to be more distinguishable for small word positions, i.e. in the very beginning of the document.
  • Fixed that User.Date with YYYY-MM-YY and DD.MM.YYYY formats gave wrong month value.
  • Crash with long words in synonym look up code was fixed.
  • Compilation problem on RedHat ES 4 was fixed.
  • Fixed that after processing a "mailto:" or a disallowed link, indexer wouldn't store crosswords from any further links on the same document