Jan Böhmer

Thats interesting. Never encountered that behavior before. It works as long as you just type a part of the name e. g. "69113771000", but if you add the last digit...

For some reason I am not able to replicate the bug anymore. It seems to work fine on the demo instance: https://demo.part-db.de/en/parts/search?name=1&category=1&description=1&mpn=1&tags=1&storelocation=1&comment=1&ipn=1&ordernr=1&keyword=691137710004 Can you please recheck if this still happens...

> F.ex. this part number 691137710004‎ Have you copied and pasted this number from your search attempts? Because it contains a non-visible control code (0x200E, Left-To-Right Marker), which prevents the...

> I created this: "1N5408G_R2_00001" from TME Right after import I searched for "1N5408G_R2_00001" and this was not found in the 1.10 I tried this and for me search shows...

I slightly modified the extraction logic, so that it at least does not split the link in half. Now it looks like this:  Its still not ideal, but I...

The sorting is done by the database, and most databases can order strings only in the binary way not the natural sorting, which you want. This is a similar problem...

Yes but that is not portable, as it does not work on MySQL and SQLite. And even then this requires a pretty new MariaDB version.

With the latest commit Part-DB supports natural sort on postgres and MariaDB 10.7+ (and via slow emulation on other platforms)

I have implemented a proper quicksearch / autocomplete search on the navbar and the new search field on homepage:  It is available in the demo instance: https://demo.part-db.de/en/

With Part-DB 1.9.0 you can now update existing parts using the info providers. It's not automatic, as you still need to review the changes and decide what to keep, but...