ioda is a fulltext indexing software, storing words and meta data. Handles logical operators, parenthesis and word distance values in queries. To use as supplement of an existing database or standalone. Runs as single prog., TCP server, CGI or library .
Be the first to post a text review of ioda fulltext engine. Rate and review a project by clicking thumbs up or thumbs down in the right column.
ioda 1.3 (internally joda 3.4 to 3.5) * Wildcards (? and *) and Regular Expressions implemented. The new parameter "extendedSearch" in the config file rules the behaviour: 0: disallow extended searches 1: allow them 2: " with one pass optimization 3: " with one pass optimization, using a temporary mem cache (for a memory btree [useMemBtree=1] this option is equal to option 2) * joda now handles six search modes. It will decide automatically, the _internal_ values are: -3: RegEx search, i.e.: /foo/ ) -2: Substring search, i.e.: *foo* ) -1: Tail search, i.e.: *foo ) 0: RegEx search AFTER head search, i.e.: /^foo.+bar/ 1: Head search, i.e.: foo* 2: Strict search, i.e.: foo ) remark: negative values will be handled in ONE PASS if allowed, this means, if the "extendedSearch" option has a value of 2 or 3 (see above). * changed Makefile to support more granular targets * log file is now relocatable. New option "logbook" in the joda config file. * merge action in libjodafulltext. currently only available in the python API. Remark: Dont't use src and bin packages from Oct 20 due to a confusion. Use them from Oct 21!
ioda 1.3 (internally joda 3.4 to 3.5) * Wildcards (? and *) and Regular Expressions implemented. The new parameter "extendedSearch" in the config file rules the behaviour: 0: disallow extended searches 1: allow them 2: " with one pass optimization 3: " with one pass optimization, using a temporary mem cache (for a memory btree [useMemBtree=1] this option is equal to option 2) * joda now handles six search modes. It will decide automatically, the _internal_ values are: -3: RegEx search, i.e.: /foo/ ) -2: Substring search, i.e.: *foo* ) -1: Tail search, i.e.: *foo ) 0: RegEx search AFTER head search, i.e.: /^foo.+bar/ 1: Head search, i.e.: foo* 2: Strict search, i.e.: foo ) remark: negative values will be handled in ONE PASS if allowed, this means, if the "extendedSearch" option has a value of 2 or 3 (see above). * changed Makefile to support more granular targets * log file is now relocatable. New option "logbook" in the joda config file. * merge action in libjodafulltext. currently only available in the python API. Remark: Dont't use src and bin packages from Oct 20 due to a confusion. Use them from Oct 21!
ioda 1.3 (internally joda 3.4 to 3.5) * Wildcards (? and *) and Regular Expressions implemented. The new parameter "extendedSearch" in the config file rules the behaviour: 0: disallow extended searches 1: allow them 2: " with one pass optimization 3: " with one pass optimization, using a temporary mem cache (for a memory btree [useMemBtree=1] this option is equal to option 2) * joda now handles six search modes. It will decide automatically, the _internal_ values are: -3: RegEx search, i.e.: /foo/ ) -2: Substring search, i.e.: *foo* ) -1: Tail search, i.e.: *foo ) 0: RegEx search AFTER head search, i.e.: /^foo.+bar/ 1: Head search, i.e.: foo* 2: Strict search, i.e.: foo ) remark: negative values will be handled in ONE PASS if allowed, this means, if the "extendedSearch" option has a value of 2 or 3 (see above). * changed Makefile to support more granular targets * log file is now relocatable. New option "logbook" in the joda config file. * merge action in libjodafulltext. currently only available in the python API. Remark: Dont't use src and bin packages from Oct 20 due to a confusion. Use them from Oct 21!
ioda 1.3 (internally joda 3.4 to 3.5) * Wildcards (? and *) and Regular Expressions implemented. The new parameter "extendedSearch" in the config file rules the behaviour: 0: disallow extended searches 1: allow them 2: " with one pass optimization 3: " with one pass optimization, using a temporary mem cache (for a memory btree [useMemBtree=1] this option is equal to option 2) * joda now handles six search modes. It will decide automatically, the _internal_ values are: -3: RegEx search, i.e.: /foo/ ) -2: Substring search, i.e.: *foo* ) -1: Tail search, i.e.: *foo ) 0: RegEx search AFTER head search, i.e.: /^foo.+bar/ 1: Head search, i.e.: foo* 2: Strict search, i.e.: foo ) remark: negative values will be handled in ONE PASS if allowed, this means, if the "extendedSearch" option has a value of 2 or 3 (see above). * changed Makefile to support more granular targets * log file is now relocatable. New option "logbook" in the joda config file. * merge action in libjodafulltext. currently only available in the python API. Remark: Dont't use src and bin packages from Oct 20 due to a confusion. Use them from Oct 21!
ioda 1.3 (internally joda 3.4 to 3.5) * Wildcards (? and *) and Regular Expressions implemented. The new parameter "extendedSearch" in the config file rules the behaviour: 0: disallow extended searches 1: allow them 2: " with one pass optimization 3: " with one pass optimization, using a temporary mem cache (for a memory btree [useMemBtree=1] this option is equal to option 2) * joda now handles six search modes. It will decide automatically, the _internal_ values are: -3: RegEx search, i.e.: /foo/ ) -2: Substring search, i.e.: *foo* ) -1: Tail search, i.e.: *foo ) 0: RegEx search AFTER head search, i.e.: /^foo.+bar/ 1: Head search, i.e.: foo* 2: Strict search, i.e.: foo ) remark: negative values will be handled in ONE PASS if allowed, this means, if the "extendedSearch" option has a value of 2 or 3 (see above). * changed Makefile to support more granular targets * log file is now relocatable. New option "logbook" in the joda config file. * merge action in libjodafulltext. currently only available in the python API. Remark: Dont't use src and bin packages from Oct 20 due to a confusion. Use them from Oct 21!
ioda 1.3 (internally joda 3.4 to 3.5) * Wildcards (? and *) and Regular Expressions implemented. The new parameter "extendedSearch" in the config file rules the behaviour: 0: disallow extended searches 1: allow them 2: " with one pass optimization 3: " with one pass optimization, using a temporary mem cache (for a memory btree [useMemBtree=1] this option is equal to option 2) * joda now handles six search modes. It will decide automatically, the _internal_ values are: -3: RegEx search, i.e.: /foo/ ) -2: Substring search, i.e.: *foo* ) -1: Tail search, i.e.: *foo ) 0: RegEx search AFTER head search, i.e.: /^foo.+bar/ 1: Head search, i.e.: foo* 2: Strict search, i.e.: foo ) remark: negative values will be handled in ONE PASS if allowed, this means, if the "extendedSearch" option has a value of 2 or 3 (see above). * changed Makefile to support more granular targets * log file is now relocatable. New option "logbook" in the joda config file. * merge action in libjodafulltext. currently only available in the python API. Remark: Dont't use src and bin packages from Oct 20 due to a confusion. Use them from Oct 21!
Be the first person to add a text review.
Copyright © 2009 Geeknet, Inc. All rights reserved. Terms of Use
Thanks for your rating!
Would you also like to write a review?