As part of our mass meta-tag burnination, we're also considering database-schema. It also seems closely related to database-design, which has been burninated and blacklisted just recently. We already have a database tag, which is not up for burnination. I don't think we need very many database-related tags since we already have a site dedicated to this: Database Administrators. I'm also thinking that it may slightly reduce the chances of receiving questions solely about databases (no code), which will get migrated to Database Administrators anyway.
\$\begingroup\$
\$\endgroup\$
1
-
\$\begingroup\$ NOTE: The action taken was synonymization, not merging. I've accepted that answer anyway since I followed a similar course of action. \$\endgroup\$– JamalJul 26, 2014 at 14:49
Add a comment
|
1 Answer
\$\begingroup\$
\$\endgroup\$
2
No, we don't. Merge them into database I say.
I just don't really see a need. There is a whole SE site dedicated to DB Administration, and schema-design/database-design is more looking at charts and concepts than code generally.
-
1\$\begingroup\$ Could you please explain your reasoning? Burnination and merging are both irreversible, so I don't want to get this wrong. \$\endgroup\$– JamalJul 25, 2014 at 16:59
-
4\$\begingroup\$ I just don't really see a need, as you said, there is a whole SE site dedicated to DB stuff, and schema-design/database-design is more looking at charts and concepts than code generally. \$\endgroup\$– PhrancisJul 25, 2014 at 17:37