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

Namespacing #63

Open
azuby opened this issue Apr 17, 2017 · 1 comment
Open

Namespacing #63

azuby opened this issue Apr 17, 2017 · 1 comment
Labels
feature-request A feature should be added or improved.

Comments

@azuby
Copy link

azuby commented Apr 17, 2017

Under the current dsl, namespacing table names for a specific environment such as staging_2_events would require loading an environment config in each model and explicitly setting the table name or monkey patching the underlying implementation.

It would be awesome if aws-record supported namespacing in an initializer or some other mechanism, similar to the way Dynamoid does so, for cases like ours where we're using a different set of table names for different environments. Thoughts?

@awood45
Copy link
Member

awood45 commented Apr 20, 2017

I'm looking at revving the version of this and revisiting some design points like this one. I agree we want this to be as easy as possible.

@mullermp mullermp added feature-request A feature should be added or improved. needs-major-version Need of a major version release to fix or implement a feature. and removed needs-major-version Need of a major version release to fix or implement a feature. labels Apr 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request A feature should be added or improved.
Projects
None yet
Development

No branches or pull requests

3 participants