Fix types of _id fields

[mdashlw]

Before you begin

• I understand my contributions may be rejected for any reason
• I understand my contributions are for the benefit of Derpibooru and/or the Philomena software
• I understand my contributions are licensed under the GNU AGPLv3

• I understand all of the above

---

I'm not sure why int and float parsers explicitly ignore spaces, didn't put that into the new parser

[Meow]

As this change has something to do with indices, this is blocked similarly to #526 (see comments on that PR)

[mdashlw]

As this change has something to do with indices, this is blocked similarly to #526 (see comments on that PR)

This only touches query parsers not indices. Should be fine to merge

[MareStare]

@mdashlw why not turn id into a numeric_field too?

[liamwhite]

it needs to support range querying

[MareStare]

Do you think it doesn't make sense to support range queries for relational IDs like image_id? IIRC it should cost nothing, right?

[MareStare]

QA

Comments

• image_id:45 correctly returns search results for the image with ID 45
• image_id: 45 with an extra space also works the same as above
• author:Pleb comments search doesn't work with Administrator account, but works when logged out. Looks like it may be an unrelated bug (created Search for comments with a specified author via an Administrator account returns zero results #558)

Galleries

• image_ids:47 search for galleries works fine, although it seems to be exposed only in JSON API

Images

• uploader_id:4 works for images

Posts

• forum_id and topic_id seem to be generally useless, so making them numeric_fields doesn't seem to change anything , or maybe I'm just missing something. Created forum_id and topic_id search query filters seem to be useless because these IDs aren't exposed anywhere #559
• user_id:4 query works as expected

Reports

• user_id:1 query works as expected
• image_id:52 works as expected
• reportable_id:240 works as expected too (generic for images, posts, and other types of objects)
• admin_id:5 works as expected filtering only reports closed by the given user ID