Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-1191

Implement a new DB development and management process

    Details

    • Type: Task Task
    • Status: Closed Closed
    • Priority: Blocker Blocker
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: 0.9.3
    • Component/s: Database
    • Labels:
      None
    • Similar issues:
      KULRICE-3139Create a new master datasource for 1.0 KC db development
      KULRICE-12998Test git with db install process
      KULRICE-7217Implement growls processing
      KULRICE-4923Implement database compatibility verification process
      KULRICE-49Document our process for making core DB changes in Rice
      KULRICE-13966Update db install process for branch changes
      KULRICE-12994Git Migration
      KULRICE-2769Implement a way to indicate whether or not the DocSearchGenerator should attempt to process result sets
      KULRICE-5595Create a new KRMS node implementation extending RequestActivationNode
      KULRICE-9970Add Hook to DD for processing beans prior to validation
    • Rice Module:
      Rice Core
    • Application Requirement:
      Rice

      Description

      Implement a plan that addresses the following aspects:

      • consuming the DB independence work done by KFS (see linked issues)
      • re-organization of DDL/SQL files into more consolidated, but module specific ANSI SQL files or Torque XML files???
      • do we want our bootstrap DB data to be in a single SQL file or in separate files to line up with each module?
      • support for multiple database products (i.e. Oracle, MySQL) and how we support generating and maintaining these in our process
      • updating existing DB related documentation - https://test.kuali.org/confluence/display/KULRICE/Database+Change+and+Migration+Policy and https://test.kuali.org/confluence/display/KULRICE/Making+a+Database+Change
      • coming out of the box with an embedded DB such as Derby
      • how to handle migration scripts and upgrades to the DB between Rice versions - how to generate these and make them part of a better upgrade process
      • automatic validation of DB changes against an embedded DB such as Derby
      • impact of 0.9.3 refactoring on module specific files

      The first step to this task should be to deal with the sub-task for putting a fully detailed plan together that addresses the issues above. Make sure the team has a chance to review and come to agreement on a process to move forward with.

        Activity

        Hide
        Aaron Godert (Inactive) added a comment -

        Nate this is the parent issue that encompasses a lot of the other issues you have on your plate. I'm cool with you closing this one as long as all of the points in this issue are covered by other separate issues.

        Show
        Aaron Godert (Inactive) added a comment - Nate this is the parent issue that encompasses a lot of the other issues you have on your plate. I'm cool with you closing this one as long as all of the points in this issue are covered by other separate issues.
        Hide
        Eric Westfall added a comment -

        Nate will be distilling this down into separate issues to more closely represent where we are currently with JPA and the KFS Torque process.

        Show
        Eric Westfall added a comment - Nate will be distilling this down into separate issues to more closely represent where we are currently with JPA and the KFS Torque process.
        Hide
        Ken Geis added a comment -

        Take a look at LiquiBase.

        "LiquiBase is an open source (LGPL), database-independent library for tracking, managing and applying database changes. It is built on a simple premise: All database changes (structure and data) are stored in an XML-based descriptive manner and checked into source control."

        http://www.liquibase.org/
        http://en.wikipedia.org/wiki/LiquiBase

        Show
        Ken Geis added a comment - Take a look at LiquiBase. "LiquiBase is an open source (LGPL), database-independent library for tracking, managing and applying database changes. It is built on a simple premise: All database changes (structure and data) are stored in an XML-based descriptive manner and checked into source control." http://www.liquibase.org/ http://en.wikipedia.org/wiki/LiquiBase

          People

          • Assignee:
            Nate Johnson (Inactive)
            Reporter:
            Aaron Godert (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Due:
              Created:
              Updated:
              Resolved:
              Start Date:

              Structure Helper Panel