Comments (6)
What version of Scenic are you running?
from scenic.
Latest - 1.2.0
from scenic.
It appears there's something about the interplay between scenic and foreigner that isn't going too well. Unfortunately, the only way to extend schema in rails is to monkey patch, and it appears our monkey patches are conflicting with each other. I'll see if there's anything I can do.
from scenic.
@sharq1 I was able to reproduce this issue with the latest foreigner (1.7.4), but can work around it by making sure foreigner
is required before scenic
. The easiest way to do this is to put foreigner ahead of scenic in your gemfile.
Does this work around work for you? Have you any interest in helping to pursue a more robust solution?
from scenic.
To be fair, I didn't test that foreigner still functions appropriately (foreign keys are dumped) when required in this manner.
from scenic.
@sharq1 Did the above workaround work for you?
from scenic.
Related Issues (20)
- "pg_stat_statements_info" already exists when running rails db:test:load HOT 6
- New Rails/MigrationClassName cop has an issue with migration filename HOT 2
- getting error Scenic::Adapters::Postgres::MaterializedViewsNotSupportedError HOT 1
- Getting "Invalid single-table inheritance type" error when using a model based on a view HOT 2
- Sequences HOT 1
- Materialization is dumped to structure.rb incorrectly HOT 2
- Is it possible to make it work with Sinatra or any other Rack app? HOT 2
- schema.rb diff after running migrations HOT 2
- How to persist `'now'::timestamp` / prevent being computed with `rails db:migrate` HOT 3
- ERB.new warnings despite #360 HOT 2
- add a support for pg_ivm ? HOT 1
- Centralise and expose configurable db views folder HOT 5
- make update_view for materialized views create less downtime HOT 1
- Add support for a cache_key and/or cache_version HOT 1
- Ignore scripts outside `db/views` folder HOT 1
- Cannot replace materialized views HOT 2
- Old migration name affecting new view name HOT 10
- cannot rollback drop_view HOT 3
- Multiple databases, main DB is assumed even though it's specified in the model. Is there a better way? HOT 1
- Feature Request: Support Generated Columns HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from scenic.