GitLab

Signed-off-by: João Victor Tozatti Risso <jvtr12@c3sl.ufpr.br>

Signed-off-by: João Victor Tozatti Risso <jvtr12@c3sl.ufpr.br>

Signed-off-by: João Victor Tozatti Risso <jvtr12@c3sl.ufpr.br>

Signed-off-by: João Victor Tozatti Risso <jvtr12@c3sl.ufpr.br>

Signed-off-by: João Victor Tozatti Risso <jvtr12@c3sl.ufpr.br>

- Eliminate throwing exceptions, ignore invalid records and report them to the user

Change the school classes task to generate SQL instead of
saving objects directly to the database through ActiveRecord.
The overhead of allocating, validating and persisting these
objects to the database is a serious bottleneck for mass insertion
of data.

This approach showed a significant boost in insertion, since
the only overhead in this case are the model validations.

However, a separate task still needs to be defined to handle the
insertion automatically using the database client or by executing
SQL queries directly from Ruby itself without the ActiveRecord
overhead. In this case, we'd have two separate tasks: one for
parsing and validating input data and a second task to ingest
these SQL queries to the underlying database.

- Add Rake task to seed the following models: AdministrativeLevel,
City, Location, Region and SchoolClassType.
- Automate database setup by enhancing the rake db:setup task.

Add presence validations to City, Location, SchoolClass and SchoolClassType models

Signed-off-by: João Victor Risso <jvtr12@c3sl.ufpr.br>