Giter VIP home page Giter VIP logo

Comments (6)

h0lg avatar h0lg commented on June 4, 2024 1

It would also be be nice to match multiple fields against the same expression. Let's assume I want to match the same query against the UTF8 and the ASCII representation of a customer name:

var index = new FullTextIndexBuilder<int>()
    .WithObjectTokenization<Customer>(o => o
      .WithId(c => c.CustomerId)
      .WithField("Customer Name", c => c.Name)
      .WithField("Customer ASCII Name", c => c.AsciiName)

If possible, I'd like a query without repetition, e.g. [Customer Name|Customer ASCII Name]=Something

Or let's assume I want to search a group of dynamic fields sharing the same same prefix or suffix -
then I'd like to query those with [prefix*]=query or [*suffix]=query.

Obviously, this can be worked around by OR-combining the same query for different field names - so it may really just a be a convenience feature for people manually writing LIFTI queries.

from lifti.

mikegoatly avatar mikegoatly commented on June 4, 2024 1

I'm going to split wildcards out to #77 - they add significant complexity and implementing this feature without them add its own value.

from lifti.

mikegoatly avatar mikegoatly commented on June 4, 2024

Nice - I like the idea of being able to wildcard a field name in the query - with a dynamic field the exact names of all the fields might not be known.

from lifti.

mikegoatly avatar mikegoatly commented on June 4, 2024

@h0lg out of interest, what's your use-case for wanting a suffix wildcard match, e.g. [*suffix]=query? I can understand the need for the prefix one to allow for searching across all dynamic fields with a given prefix, but I'm not sure about the suffix one.

from lifti.

h0lg avatar h0lg commented on June 4, 2024

@h0lg out of interest, what's your use-case for wanting a suffix wildcard match, e.g. [*suffix]=query? I can understand the need for the prefix one to allow for searching across all dynamic fields with a given prefix, but I'm not sure about the suffix one.

I could get the idea to group fields by a common name suffix instead of a common name prefix;

e.g. if I wanted to search Customers from your above example by [* Name]=Mike.

from lifti.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.