We could, but in that case the caller may as well have just added a `rescue nil`. This avoids the error in the first place, which isn't that big of deal for just rails, but if you have monitoring on the database that watches for database errors, this avoids the database error in the first place.

This could be less complex by doing `*args` and`options = args.extract_options!`, but that would mean refactoring `index_name_for_remove` and `index_name` which also have similar checks for "is this a column name or an options hash"

I could also get rid of the `respond_to?` by always swallowing the `StatementInvalid`, but that might swallow other errors that wouldn't otherwise be hidden (like say, a permissions error).