Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ffcrm does not namespace it's tables or use a separate schema when used as an engine #184

Open
timuckun opened this issue Aug 1, 2012 · 4 comments
Labels
Milestone

Comments

@timuckun
Copy link

timuckun commented Aug 1, 2012

the tables should have a prefix or if using postres it should be possible to have it install into it's own schema ( this might also work with later versions of mysql)

@timuckun
Copy link
Author

timuckun commented Aug 1, 2012

The models should also be namespaced for engine usage.

@steveyken
Copy link
Member

Using "isolate_namespace" would help us here... http://apidock.com/rails/v3.2.3/Rails/Engine

@timuckun
Copy link
Author

timuckun commented Aug 2, 2012

You would still need to namespace your models, controllers etc but
that's probably a good idea no matter what.

On Thu, Aug 2, 2012 at 2:27 PM, Steve Kenworthy
[email protected]
wrote:

Using "isolate_namespace" would help us here... http://apidock.com/rails/v3.2.3/Rails/Engine


Reply to this email directly or view it on GitHub:
#184 (comment)

@johnnyshields
Copy link
Contributor

This feature should be added IMHO.

@johnnyshields johnnyshields added this to the 0.20.0 milestone Jan 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants