This project is archived and is in readonly mode.
Module specific table_name_prefix
-
José Valim
- Assigned user changed from José Valim to Jeremy Kemper
- Milestone cleared.
Assigning to Jeremy Kemper, he's the best person to give feedback on this.
-
Andrew White
Updated patch to apply to latest master - just offsets, no code changes.
-
Repository
- State changed from new to resolved
(from [5f7bc47303933ec67700f6390c98d889f6d9b0d1]) Rename modularized_table_name_prefix to full_table_name_prefix [#4032 Module specific table_name_prefix state:resolved] http://github.com/rails/rails/commit/5f7bc47303933ec67700f6390c98d8...
-
Yehuda Katz (wycats)
Applied. Would you mind backporting this to 2.3?
-
Jeremy Kemper
- State changed from resolved to open
- Milestone set to 2.3.6
-
Andrew White
Backport to 2.3 patch with the method renamed to full_table_name_prefix
-
Repository
- State changed from open to committed
(from [03d5d0b5f50161d8ec1b2b627e483aad7100494a]) Add the ability to specify table_name_prefix on individual modules
[#4032 Module specific table_name_prefix state:committed]
Signed-off-by: Jeremy Kemper jeremy@bitsweat.net
http://github.com/rails/rails/commit/03d5d0b5f50161d8ec1b2b627e483a... -
phs
cross linking #4230 [PATCH] AR migration generator includes model's modules in table name. . The question is whether the module-specific stuff in this patch can be harnessed in the model generator.
