aboutsummaryrefslogtreecommitdiffstats
path: root/db/migrate
Commit message (Collapse)AuthorAgeLines
* fixup! Use translation tables for PublicBodyCategory and PublicBodyHeadingLouise Crow2014-09-26-2/+8
|
* fixup! Use translation tables for PublicBodyCategory and PublicBodyHeadingLouise Crow2014-09-25-1/+7
|
* fixup! Add display order to public body categories and headingsLouise Crow2014-09-24-2/+0
|
* Add display_order field to public_body_headings.Louise Crow2014-09-22-1/+2
| | | | # Please enter the commit message for your changes. Lines starting
* Add display order to public body categories and headingslizconlan2014-09-22-0/+16
|
* Use translation tables for PublicBodyCategory and PublicBodyHeadinglizconlan2014-09-22-0/+151
|
* Replace existing PublicBodyCategories functionality with db models ↵lizconlan2014-09-22-0/+27
| | | | PublicBodyCategory and PublicBodyHeading
* Merge branch 'issues/1709-api-controller-speed' into rails-3-developLouise Crow2014-08-04-0/+5
|\
| * Add an index for event_type on info_request_eventsSteven Day2014-08-01-0/+5
| | | | | | | | | | | | | | Selecting request events for a particular body is slow because we need to filter the events by event_type and don't currently have an index on that field. This should speed that up. Closes #1709
* | Rename XXX comments with TODO:Gareth Rees2014-06-10-6/+6
| | | | | | | | Picks these up in `rake notes` and adds semantic meaning
* | Define track things constraint correctlyGareth Rees2014-05-28-0/+17
|/ | | | | | | | > The constraint fk_track_request_public_body on > track_things_sent_emails is defined incorrectly, referring to user_id > rather than public_body_id. Via Robin Houston
* Add default blank string to PublicBody@short_nameGareth Rees2014-04-09-0/+11
| | | | The validation allows a blank short_name but the schema does not.
* Add SpamAddress modelGareth Rees2014-03-26-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The volume of spam in the holding pen in WDTK has increased. Over a few weeks in January 2014 the pattern was roughly: - 8 were sent "To" the same address, which was a nearly valid old request address - correct hash, but missing the second hyphen. - 1 was sent "To" an invalid request address (nearly correct hash) - 1 was sent "BCC" a valid request address - 1 was sent "BCC" request@whatdotheyknow.com If a spam was sent "To" an old valid request address then it would be rejected. It's not entirely safe to just reject mails to old requests with any hash, because sometimes authorities miss out a digit in the request number, though perhaps simply getting a failure bounce would cause them to check. In any case that wouldn't trivially catch the most frequent case above as it doesn't have an obvious request number. --- We looked at greylisting and configuring the MTA with an RBL. Greylisting was rejected as it would slow down the responsiveness of the application when people email in. This could be revisited if/when emails are parsed through a queue system depending on how we find the performance there. An RBL is already configured, but this ticket refers more to where the email is sent rather than who it came from. --- We elected to: - Create spam_address model - Add code to RequestMailer.receive to check the list of spam addresses and silently discard an incoming mail if it's addressed to one of them - Add page to admin interface for adding/removing spam addresses --- Thanks to Ganesh Sittampalam for the research and Louise Crow for the implementation strategy.
* Merge branch 'feature/batch-requests' into rails-3-developLouise Crow2014-01-29-0/+51
|\ | | | | | | | | | | Conflicts: config/general.yml-example spec/factories.rb
| * Simplify return value, set sent_at in create_batch!Louise Crow2013-12-04-0/+5
| |
| * Add association between batches and public bodies.Louise Crow2013-12-04-0/+8
| |
| * Add check for double submission.Louise Crow2013-12-04-0/+11
| |
| * Add InfoRequestBatch model.Louise Crow2013-12-04-0/+22
| | | | | | | | | | Re-annotate models. Index InfoRequestBatches by user - we'll display the batches for a user when they view their own requests.
| * Add a can_make_batch_requests flag to user modelLouise Crow2013-12-04-0/+5
| | | | | | | | Make it updatable via the user admin page.
* | Form and models for asking for a public body change.Louise Crow2014-01-13-0/+20
|/
* Add a info_requests_visible_classified_count column to PublicBodyMark Longair2013-11-05-0/+15
| | | | | | This counts only those info requests that have prominence 'normal' (i.e. are not hidden) and are not 'awaiting_description' (i.e. that they have had some basic status classification).
* Merge branch 'feature/hide-individual-responses' into rails-3-developLouise Crow2013-09-17-0/+25
|\ | | | | | | | | | | | | | | | | | | | | Conflicts: Gemfile app/views/admin_request/edit_outgoing.html.erb config/packages doc/CHANGES.md doc/INSTALL.md spec/models/info_request_spec.rb spec/models/public_body_spec.rb
| * Add prominence fields to outgoing message.Louise Crow2013-09-16-0/+6
| |
| * Adding prominence_reason to IncomingMessage.Louise Crow2013-09-16-0/+5
| |
| * Add prominence to incoming message.Louise Crow2013-09-16-0/+5
| |
| * Remove prominence.Louise Crow2013-09-16-0/+9
| | | | | | | | | | | | | | Add a migration to remove the unused column 'prominence' from info_request_events, remove validation of prominence, remove unused InfoRequestEvent.user_can_view? method. Remove references to InfoRequestEvent.prominence.
* | Add a page with experimental statistics on public bodiesMark Longair2013-08-20-0/+26
|/ | | | | | | | | | | | | | | | | The statistics on the status of the requests to a particular public body are too slow to calculate on-the-fly, so this commit adds: * Extra columns on public_bodies to store counts of the successful, not held, and overdue request counts for each public body. * A rake task which should be run periodically to update the overdue request count column. If Javascript is not available, the summary statistics are shown as tables. If Javascript is available, graphs are drawn with Flot.
* Update reference to Configuration to reflect name change to ↵Louise Crow2013-04-30-1/+1
| | | | AlaveteliConfiguration
* Update syntax while I'm hereHenare Degan2013-03-05-1/+1
|
* Remove debugging output that was causing migration to failHenare Degan2013-03-05-2/+0
|
* Merge branch 'develop' into rails-3-spikeHenare Degan2013-02-15-4/+2
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: Gemfile Gemfile.lock app/controllers/general_controller.rb app/controllers/track_controller.rb app/models/outgoing_message.rb app/models/public_body.rb app/models/user.rb app/views/general/frontpage.rhtml config/environment.rb config/initializers/inflections.rb config/initializers/mime_types.rb db/migrate/094_remove_old_tags_foreign_key.rb lib/timezone_fixes.rb spec/models/request_mailer_spec.rb spec/views/request/list.rhtml_spec.rb
| * Drop the obsolete indexes explicitly by name - the 'remove_index' calls ↵Louise Crow2013-01-17-4/+2
| | | | | | | | don't work as the table has been renamed, and they automatically generate the index name from the table name. Apply custom index name from a5e90e2b7ea6adedbf80c05bbb84425a02c63da0.
| * Fix up some DB migration issues with Rails 3Henare Degan2013-01-18-3/+4
| | | | | | | | | | * The public_body_tags table had already been removed * The index has_tag_string_tags generated a name longer than the Postgres maximum of 63 characters. It was ignored in earlier Rails versions, see: https://rails.lighthouseapp.com/projects/8994/tickets/6187-postgresql-and-rails-303-migrations-fail-with-index-name-length-64-chars
* | We expect timestamps in a later migration but they're no longer added by the ↵Henare Degan2013-01-22-0/+2
| | | | | | | | newer version of acts_as_versioned we're using since 2ba57e8
* | Fix up some DB migration issues with Rails 3Henare Degan2012-12-11-3/+4
|/ | | | | * The public_body_tags table had already been removed * The index has_tag_string_tags generated a name longer than the Postgres maximum of 63 characters. It was ignored in earlier Rails versions, see: https://rails.lighthouseapp.com/projects/8994/tickets/6187-postgresql-and-rails-303-migrations-fail-with-index-name-length-64-chars
* Remove old code.Louise Crow2012-11-20-10/+2
|
* The used sql syntax is not supported by sqlite. Now db:migrate works with ↵Stefan Langenmaier2012-11-19-4/+11
| | | | sqlite.
* Add migration to add disclosure_log fieldMatthew Landauer2012-10-22-0/+13
|
* Rename models and tables exim -> mail_serverMatthew Landauer2012-10-11-0/+13
|
* Merge remote-tracking branch 'openaustralia_github/configuration_refactor' ↵Louise Crow2012-10-01-1/+1
|\ | | | | | | | | | | | | into develop Conflicts: config/general.yml-example
| * Extract configuration with defaults into one moduleMatthew Landauer2012-09-25-1/+1
| |
* | Re-enable migration - it looks like the underlying bug is something to do ↵Louise Crow2012-09-27-56/+56
| | | | | | | | with interlock/memcached.
* | Test commit to try to figure out what's wrong with the travis build - it ↵Louise Crow2012-09-27-56/+56
|/ | | | always fails on this migration.
* Merge remote-tracking branch 'origin/release/0.6.6' into developLouise Crow2012-09-20-4/+3
|\
| * Faster way to update counter cache.release/0.6.6Louise Crow2012-09-20-4/+3
| |
* | Migration accidentally omitted from 550f143Robin Houston2012-09-19-0/+9
|/
* Add index on updated_at to public body versions as this is how they are ↵Louise Crow2012-09-13-0/+9
| | | | retrieved in the admin timeline view.
* Add some indexes to help IncomingMessage.fully_destroy find records more ↵Louise Crow2012-09-13-0/+18
| | | | efficiently by info_request_event_id
* Add an index on incoming message id to the outgoing messages table - suspect ↵Louise Crow2012-09-13-0/+9
| | | | this will improve the performance of AdminRequestController#destroy_incoming, which looks for outgoing messages by incoming message.
* Add a counter cache for the number of info_requests associated with public ↵Louise Crow2012-09-12-0/+17
| | | | bodies.