New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Searching numbers is functionally broken #30

Closed
Beep6581 opened this Issue Dec 5, 2017 · 3 comments

Comments

Projects
None yet
2 participants
@Beep6581

Beep6581 commented Dec 5, 2017

Last reproduced in 9.4.0.5188 though it's been like this since I started using HeidiSQL two years ago.

A bigint column is formatted for example like this:
99 015 124 722 666
which is fine when viewing data, is makes reading it much easier.

If you edit the field, it changes to
99015124722666
No spaces. Fine again.
imgur-2017_12_05-12 13 55

However, if you want to search for "22666", 0 matches.
Why? Because you actually have to search for "22 666", notice the whitespace.

The digit grouping symbol - whitespace - should be only used for presentation, not when searching!

imgur-2017_12_05-12 12 15

@ansgarbecker

This comment has been minimized.

Show comment
Hide comment
@ansgarbecker

ansgarbecker Dec 5, 2017

Collaborator

I guess I could temporarily disable local number formatting while the search dialog is open.

Collaborator

ansgarbecker commented Dec 5, 2017

I guess I could temporarily disable local number formatting while the search dialog is open.

@ansgarbecker

This comment has been minimized.

Show comment
Hide comment
@ansgarbecker

ansgarbecker Dec 5, 2017

Collaborator

Should work as expected in latest nightly build, which is on the way to be compiled.

Collaborator

ansgarbecker commented Dec 5, 2017

Should work as expected in latest nightly build, which is on the way to be compiled.

@Beep6581

This comment has been minimized.

Show comment
Hide comment
@Beep6581

Beep6581 Dec 5, 2017

@ansgarbecker fix confirmed, thank you!

Beep6581 commented Dec 5, 2017

@ansgarbecker fix confirmed, thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment