Uploaded image for project: 'Poulpe'
  1. Poulpe
  2. POULPE-218

Migrating from "Table per class hierarchy" schema to "Table per subclass" schema

VotersWatchers
    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.13 swallows
    • Fix Version/s: 0.13 swallows
    • Labels:
      None

      Description

      Need to save COMMON entities unchanged. Under current "Table per class hierarchy" schema we can't transparently moving COMMON data between different projects.

        Attachments

          Structure

            Activity

              People

              • Assignee:
                alexandreteterin@gmail.com Alexandre Teterin
                Reporter:
                alexandreteterin@gmail.com Alexandre Teterin
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 10h Original Estimate - 10h
                  10h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 11h
                  11h

                    Structure Helper Panel