How can I search part of word ?

[Phone Jack]

I have a record containing the word "Jack". I conduct search with *ac* but result returned NOT FOUND.

Is there any way out ?

Thanks.

[Rainer Eberhardt]

Same problem here.
Search works most of the time, but sometimes not: No error message, just no search results.

Any help? That's quite a "biggie" for me.
Thanks

[WetMike]

I believe that the * only works at the end of a word so you would need to look for Jac* or Ja*

I also thought that ? was supposed to work for a single character so in theory Jac? would work, but I have not managed to get this to work.

I agree with you that the search generalities do not seem to be good.  :-(

[John Ukos]

 I have also been frustrated by this and got a response from the developer Vasiliy Egorov back in July of 2015 and he said "This limitation of the used search engine.In future versions I will try to improve the search."  So hopefully this will get fixed.

John

[G N]

Exactly

Till date partial word search is not fixed

Lets say any field contains a word jack,

Ac or a k all should give me result

[G N]

For a database app
Search is extremely important

[Bill Crews]

I'm not sure what you may already know about, so I'll paste the wiki section about Search below.

It seems that the * operator works only on the tail end of a field value, not on the front. So, for Jack, you can say j* or ac* and get Access or action, but you can't say *ac* to get Jack or lacquer.

The criteria available for the script function are identical to those for the user interface, so if you find documentation for one, it should also apply to the other.

I don't believe the search/find functionality has changed in a very long time. In case it has, and I just didn't catch it, please try search keys like *ac*. It might work. If it does, please report back, so I can update the wiki with your new information.

Keep in mind that we in this forum are users like yourself, not the developer.

Search

Pressing the magnifying-glass Search icon in the upper-right portion of the screen opens a text box at the top of the screen for entry of a search key. A list of recently-used search keys is displayed, allowing the user to readily repeat a recent search.

As the user types the search key, the list of recent search keys is replaced by a list of matching entry identifiers (concatenated Name fields) with the library. If one of them is selected, the entry is opened in an Entry View card.

If Enter is pressed instead, the search is executed based on the key value entered, and all entries containing a match in any searchable field are listed.

Search is supported not only for unencrypted libraries, but also for encrypted libraries.

Advanced search keys

You can use the asterisk (*) to substitute for any number of characters in a row on the tail end of a keyword.

For example, if you search for gloss*, all entries containing words beginning with gloss will be found.

The query syntax supports the OR binary set operator. The operator must be entered using capital letters.

For example, if you search for sqlite OR database, all entries containing words sqlite or database will be found.

The query syntax supports a unary "-" operator that may be applied to basic term and term-prefix queries. Use sqlite -database to search for the set of entries that contain the term sqlite but do not contain the term database.

Examples

String Result

Memento is the best database application on android

Search

Memento* (finds any field beginning with 'Memento')

Search

best application (finds fields containing both 'best' and 'application' within the field)

Searching libraries using barcodes

To enable scanning of barcodes:

1. Install “Barcode Scanner” by ZXing Team (also available to download through Memento interface).
2. Set up a field with the Barcode field type.

When the above criteria have been met, open the context menu > Barcode search; then scan the barcode.

[ARant]

I don't think 'the unary "-" operator' works according to the 'Search' Wiki entry in the current Memento version (Android v9.0) .. search query 'aaa -bbb' returns a bunch of entries containing both 'aaa' _and_ 'bbb' !?

[Bill Crews]

Well, then, I suggest contacting the developer at sup...@MementoDatabase.com, cuz it's a bug. Give him enough info to recreate the problem on his end. Maybe export your library with data as a template and send it to him.

--
You received this message because you are subscribed to the Google Groups "mementodatabase" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mementodataba...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mementodatabase/9721c5f1-27b5-430e-9a99-5f3e0949f581%40googlegroups.com.

[ARant]

The developer suggested reindexing the database (Settings -> Reindex). I tried that and found out that selecting 'Unicode61' lexical analyzer sorted out the problem. Reindexing with 'Default' or 'ICU' didn't help. Maybe there is some space for improvement in choosing the default lexical analyzer or a prominent note concerning searches and reindexing in user documentation ?

To unsubscribe from this group and stop receiving emails from it, send an email to memento...@googlegroups.com.

[John Ukos]

I have tried re-indexing with all three options with no joy.

[Bill Crews]

I hope I'm not getting this wrong, but upon rereading the wiki today, I see the following...

Search

best application (finds fields containing both 'best' and 'application' within the field)

That works this way fine on my device. Where is key1-key2 mentioned? If it is mentioned, it's wrong and I'll fix the wiki. Just enter key1 key2.

To unsubscribe from this group and stop receiving emails from it, send an email to mementodataba...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mementodatabase/77e923d3-0f40-4e56-9c53-7a52b6666e9e%40googlegroups.com.

[John Ukos]

My bad. I was thinking that reseting index would fix the search any part of text issue. I realize this was an attempt to fix the key 1/2 issue. Sorry for the confusion.

To view this discussion on the web visit https://groups.google.com/d/msgid/mementodatabase/77e923d3-0f40-4e56-9c53-7a52b6666e9e%40googlegroups.com.

[Bill Crews]

No problem. It's good that members report behavior they feel is problematic to the rest of us, so thanks.

To unsubscribe from this group and stop receiving emails from it, send an email to mementodataba...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mementodatabase/c86798ab-d340-4f66-9bc8-f207da4440c9%40googlegroups.com.

[Il Re Enomis]

Has there been an update to this one? I am having issues searching for substrings on the desktop app (like 'ac' for Jack returns no result). Wildcards (*) do not help. I'm on version 3.1.0. Thank you.

[Gencin Biri]

Same here. DS-2cd2347g2h-liu  when i search for 2347 i get no results. Any fix ?

Op donderdag 30 november 2023 om 16:51:21 UTC+1 schreef Il Re Enomis:

[David Gilmore]

Have you tried reporting this possible bug to Memento directly? Memento staff does not always read this forum.

[Mmm]

Попробуйте sql поиск:

SELECT * FROM table_name WHERE name LIKE '%2347%';

четверг, 17 апреля 2025 г. в 19:37:39 UTC+3, aa6...@gmail.com:

[John Ukos]

Where do I enter that script and how do I launch it?

[Amundsf]

Hi

Push search icon -> SQL-icon in tipper right corner. 

[Amundsf]

Hi again

I have tested in my test and added DS-2cd2347g2h-liu into a text field. I can then add a FILTER with type "Contains" like 2347 and the value is found. So that is probably a easier solution than using SQL. 

I repdroduce that search icon don't give any values for 2347 or *2347*.

It's a bit strange because *eik* return value that is Eika.  But *es* don't return value Test. 

Amund 

[Amundsf]

Fortet about the last part about *Eik* finds "Eika" (but "es" not finding "Test"), that was because wildcard (*) ony work at the end as described in one of the frist posts in this thread. 

I had just forgotten that my test library have two fields on entry name, so I didn't see that the field started with Eika 🙈😅