Rake db migrate not updating schema
— Reply to this email directly or view it on Git Hub (#55 (comment)).pg_stat_statements() pg_stat_statements(userid, dbid, query, calls, total_time, rows, shared_blks_hit, shared_blks_read, shared_blks_dirtied, shared_blks_written, local_blks_hit, local_blks_read, local_blks_dirtied, local_blks_written, temp_blks_read, temp_blks_written, blk_read_time, blk_write_time); Reloading a schema from scratch (on development or test) is causing an error when Active Record attempts to recreate views that are already present in the database (in my case, it was `pg_stat_statements`).OR if someone is currently facing this issue and they come here via googling around they should really share an example app!
This leads to a more general point: whenever you create a migration, check to make sure it can be rolled back and migrated successfully.CREATE VIEW pg_stat_statements AS SELECT pg_stat_statements.userid, pg_stat_statements.dbid, pg_stat_statements.query, pg_stat_statements.calls, pg_stat_statements.total_time, pg_stat_statements.rows, pg_stat_statements.shared_blks_hit, pg_stat_statements.shared_blks_read, pg_stat_statements.shared_blks_dirtied, pg_stat_statements.shared_blks_written, pg_stat_statements.local_blks_hit, pg_stat_statements.local_blks_read, pg_stat_statements.local_blks_dirtied, pg_stat_statements.local_blks_written, pg_stat_statements.temp_blks_read, pg_stat_statements.temp_blks_written, pg_stat_statements.blk_read_time, pg_stat_statements.blk_write_time FROM () pg_stat_statements(userid, dbid, query, calls, total_time, rows, shared_blks_hit, shared_blks_read, shared_blks_dirtied, shared_blks_written, local_blks_hit, local_blks_read, local_blks_dirtied, local_blks_written, temp_blks_read, temp_blks_written, blk_read_time, blk_write_time); Due to some migrations in my history that rely on gems no longer in my application and a large number of total migrations, I'd like to avoid having to edit old migrations and/or temporarily patch them any time I rebuild the db from scratch.Due to a Rails 4.1 bug with rolled-back, edited, and re-played migrations, Hmmm, I've never tried loading schema on a populated database. I thought you were supposed to reset the database instead?The MIT License (MIT) Copyright (c) 2011-2014 makandra Gmb H Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
I'm wondering if it's trying to drop a different database somehow.