Inconsistent results when using eq

[koaning]

Bug report

Describe the bug

I have a query that runs just as expected.

> supabase.table("storage").select('*').ilike('message', 'dude').execute()
{'data': [{'id': 2,
   'inserted_at': '2021-07-27T18:34:27.084558+00:00',
   'updated_at': '2021-07-27T18:34:27.084558+00:00',
   'email': '[email protected]',
   'message': 'dude'},
  {'id': 3,
   'inserted_at': '2021-07-27T18:34:31.482083+00:00',
   'updated_at': '2021-07-27T18:34:31.482083+00:00',
   'email': '[email protected]',
   'message': 'dude'}],
 'status_code': 200}

But notice what happens when I run:

> supabase.table("storage").select('*').like('email', '[email protected]').execute()
{'data': [], 'status_code': 200}

Somehow I cannot query the email like I can the other columns in my table. Is email a protected value?

I am using supabase-py version 0.0.2.

[willtraweek]

I've been running into the same issue. When I started playing around with it, it looks like its a problem with the way the URLs are encoded.

For example, when I set an email to test and execute the query with that value, then the row shows up just fine. Same with test@test, but [email protected] shows no results.

[willtraweek]

I'm beginning to think this is because they use a . to differentiate between the command and the query itself. See the URL that .eq("email", "[email protected]") produces: