Open filiptibell opened 1 month ago
What should the query syntax for this look like? Or would this be better purposed for a new widget allowing for more specific search semantics? This kind of stuff is really expensive, as not only does jabby have to convert all the data into LON, but it also needs to perform string pattern matching (which gets expensive on large tables)
If this was to be part of the querying widget, syntax could change to do something like:
equal(Data, "some plain string")
find(Data, "find this string")
match(Data, "match this pattern")
If this was to be part of the querying widget, syntax could change to do something like:
equal(Data, "some plain string")
find(Data, "find this string")
match(Data, "match this pattern")
I definitely think it should be part of the query widget. The proposed syntax looks fine to me!
Our games (tycoons) have a lot of different entities where it might be interesting to look at single entities that a player "owns" to diagnose issues they may be having. Fortunately, we follow a naming scheme like
Section1Name1
,Section2Name1
and they are easy enough to find in the debugger, it just takes a lot of page flipping and scrolling. These names are set directly on entities and the name component is also the component we use as the "debug" component in jabby.For our use cases any of the following would help browsing entities quicker:
string.sub(name, 1, #needle) == needle
)string.find(name, needle, 1, true)
)string.match(name, ...)
)