Bug #38352 | MATCH ... AGAINST ... WITH PARSER ... | ||
---|---|---|---|
Submitted: | 24 Jul 2008 17:56 | Modified: | 24 Jul 2008 18:42 |
Reporter: | Hartmut Holzgraefe | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: FULLTEXT search | Severity: | S4 (Feature request) |
Version: | 5.1 | OS: | Any |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[24 Jul 2008 17:56]
Hartmut Holzgraefe
[25 Jul 2008 10:52]
Hartmut Holzgraefe
There are also use cases with data that is not really textual where stored and queried data may differ in format/syntax/encoding but comes down to the same tokens being used internally. I'm thinking about a protein database right now where - rows store DNA/RNA nucleotide sequences using the A-C-G-T or A-C-G-U "alphabet" - queries search for amino acid sequences instead using one letter acid codes - the indexed tokens are nucletide triplets - from the input alone it is not clear whether the sequence "GAC" is - the nucleotide triplet codon for Alanine - the amino acid sequence Glycine-Alanine-Cysteine Here a combination of FULLTEXT ... WITH PARSER dna_sequence; and MATCH .. AGAINST ('G A C') WITH PARSER dna_sequence; MATCH .. AGAINST ('G A C') WITH PARSER rna_sequence; MATCH .. AGAINST ('G A C') WITH PARSER amino_sequence; would be needed to allow different queries against a DNA sequence database