Acts as searchable verify that the @project_id@ and @created_on@ columns exists when not providing @project_key@ and @date_column@ options in the model defined to be searchable.
When one of those options is not set, an error is raised when the corresponding column (or the entire table) doesn't exists by loading the model.

I think that loading time is not the right moment for doing this verification. None of the rails mechanisms prevent a model to be loaded because of missing column in the database.

This defect causes me problem during initial @rake db:migrate@ when loading a conf that loads some models that are searchable.

Here is a patch that solves the problem.