Namespacing

Open
#63 1 comment 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
ruby
Domain
database

Research direction

Start by reviewing the current DSL and the initializer or configuration entry points mentioned in the issue. Compare the per-model environment configuration and monkey-patching approaches with the requested mechanism, then define what support for environment-specific table names should look like without those workarounds.

Written by the indexing model from the issue text.

Description

feature-request

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?

Dominant language
Ruby
Stars
318
Forks
44
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws/aws-record-ruby

All issues in aws/aws-record-ruby

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.