mirror of
https://github.com/openSUSE/osem.git
synced 2026-08-13 19:54:02 +00:00
Furrest City's modified version of OSEM
http://osem.io
fdd7806071
When running migration 20170705075039 followed by 20170715131706, the
latter fails due to lingering null values in a newly non-null column—
Mysql2::Error: Invalid use of NULL value: ALTER TABLE `tracks` CHANGE `state` `state` varchar(255) DEFAULT 'new' NOT NULL
db/migrate/20170715131706_make_track_state_not_null_and_add_default_value.rb:17:in `change'
—despite having apparently converted any existing null values prior to
changing the column type. Investigation reveals that actually the
attempted conversion has had no effect, and that this can be resolved by
clearing ActiveRecord internal caches between migrations:
connection.schema_cache.clear_data_source_cache! 'tracks'
The same problem also affects running 20170705075039 followed by
20170720134353, but in that case it leads to silent data corruption as
`change_column_null` automatically converts any lingering null values.
This commit 1) clears ActiveRecord internal caches at the beginning of
each affected migration, and 2) replaces `change_column_null` with
`change_column` to reflect that no automatic conversion is intended.
|
||
|---|---|---|
| .github | ||
| app | ||
| bin | ||
| config | ||
| db | ||
| dist | ||
| doc | ||
| lib | ||
| public | ||
| spec | ||
| vendor | ||
| .codecov.yml | ||
| .dockerignore | ||
| .gitignore | ||
| .haml-lint.yml | ||
| .haml-lint_todo.yml | ||
| .overcommit.yml | ||
| .rubocop.yml | ||
| .rubocop_todo.yml | ||
| .ruby-gemset | ||
| .ruby-version | ||
| app.json | ||
| CHANGES.md | ||
| CODE_OF_CONDUCT.md | ||
| config.ru | ||
| CONTRIBUTING.md | ||
| docker-compose.override.yml.example | ||
| docker-compose.yml | ||
| docker-compose.yml.production-example | ||
| Dockerfile | ||
| Dockerfile.production | ||
| dotenv.example | ||
| Gemfile | ||
| Gemfile.lock | ||
| Guardfile | ||
| INSTALL.md | ||
| LICENSE | ||
| Procfile | ||
| Rakefile | ||
| README.md | ||
Open Source Event Manager - osem.io
An event management tool tailored to Free and Open Source Software conferences.
Installation
Please refer to our installation guide.
How to contribute to OSEM
Please refer to our contributing guide.
Contact
GitHub issues are the primary way for communicating about specific proposed changes to this project. If you have other questions feel free to subscribe to the opensuse-web@opensuse.org mailinglist, all OSEM contributors are on that list! Additionally you can use #osem channel on freenode IRC.