You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ran into a weird problem (Running docker desktop on M1 Mac):
When I do some exact string matches (SELECT * FROM table where name='Sample Name'), for some strings, it will return 0 results even though I can confirm there is a record with that string (by matching with the ID pkey). However, this does work if I do SELECT * FROM table where name LIKE '%Sample Name'. I've confirmed through looking at the raw bytes that there are no characters in front of the name.
However, if I change the version to the non-alpine version, SELECT * FROM table where name='Sample Name' starts returning the row as expected. I'm not sure why this is the case at all.
The text was updated successfully, but these errors were encountered:
I fixed this for now by taking a database dump (while on the non-alpine version), deleting the volume, re-creating the volume, and importing the dump again into postgres while on alpine.
Ran into a weird problem (Running docker desktop on M1 Mac):
When I do some exact string matches (
SELECT * FROM table where name='Sample Name'
), for some strings, it will return 0 results even though I can confirm there is a record with that string (by matching with the ID pkey). However, this does work if I doSELECT * FROM table where name LIKE '%Sample Name'
. I've confirmed through looking at the raw bytes that there are no characters in front of the name.However, if I change the version to the non-alpine version,
SELECT * FROM table where name='Sample Name'
starts returning the row as expected. I'm not sure why this is the case at all.The text was updated successfully, but these errors were encountered: