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

Analysis: Rename KRAD database tables

        Details

        • Type: Task Task
        • Status: Closed Closed
        • Priority: Major Major
        • Resolution: Complete
        • Affects Version/s: None
        • Fix Version/s: 2.4
        • Component/s: Database, Roadmap
        • Security Level: Public (Public: Anyone can view)
        • Labels:
          None
        • Similar issues:
          KULRICE-4992Review and rename tables/columns in master database
          KULRICE-4734Rename kr web folder to krad
          KULRICE-7448Database upgrade scripts should not drop tables
          KULRICE-5335Database Changes for Category
          KULRICE-11640Analysis for maintenance global documents on KRAD
          KULRICE-2320Refactor Rice table names to conform to database naming standards
          KULRICE-10744Create database scripts for KNS/KRAD conversion
          KULRICE-6684Rename KRAD Jsp for application view
          KULRICE-2948Rename TARGET_PRIMARY_KEY column on certain KIM tables
          KULRICE-7945Implement Referential Integrity on KEW database tables
        • Rice Module:
          KRAD
        • Sprint:
          2.4.0-m4 KRAD Sprint 3
        • KAI Review Status:
          Not Required
        • KTI Review Status:
          Not Required
        • Include in Release Notes?:
          Yes

          Description

          Currently the tables backing KRAD still have krns (for KNS) in the name. New tables are being created as krad_. To be consistent we need to rename the old tables to krad_

            Issue Links

            cloned from

            Bug Fix - A problem which impairs or prevents the functions of the product. KULRICE-7208 Template

            • Major - Major loss of function.
            • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
            relates to

            Rice Enhancement - An item to be included in a roadmap KRRM-144 KRAD Equivalency with KNS

            • Major - Major loss of function.
            • Open - The issue is open and ready for the assignee to start work on it.

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Kristina Taylor (Inactive) added a comment -

              Are you talking about all these tables?

              krns_adhoc_rte_actn_recip_t
              krns_att_t
              krns_doc_hdr_t
              krns_doc_typ_attr_s
              krns_lock_s
              krns_lookup_rslt_s
              krns_lookup_rslt_t
              krns_lookup_sel_t
              krns_maint_doc_att_lst_t
              krns_maint_doc_att_s
              krns_maint_doc_att_t
              krns_maint_doc_t
              krns_maint_lock_s
              krns_maint_lock_t
              krns_nte_s
              krns_nte_t
              krns_nte_typ_t
              krns_pessimistic_lock_t
              krns_sesn_doc_t

              Show
              Kristina Taylor (Inactive) added a comment - Are you talking about all these tables? krns_adhoc_rte_actn_recip_t krns_att_t krns_doc_hdr_t krns_doc_typ_attr_s krns_lock_s krns_lookup_rslt_s krns_lookup_rslt_t krns_lookup_sel_t krns_maint_doc_att_lst_t krns_maint_doc_att_s krns_maint_doc_att_t krns_maint_doc_t krns_maint_lock_s krns_maint_lock_t krns_nte_s krns_nte_t krns_nte_typ_t krns_pessimistic_lock_t krns_sesn_doc_t
              Hide
              Permalink
              Kristina Taylor (Inactive) added a comment - - edited

              For the analysis we need to do the following:

              1. Determine which tables are candidates for the change
              2. Analyze how tables are used and which tables will be deprecated for KRAD
              3. Ask Jerry to confirm results

              I started an analysis document: https://docs.google.com/a/kuali.org/spreadsheet/ccc?key=0AqGzZp-mOGfNdEdSUzdRYXVCa3BubkZ6eWxScEJtSUE#gid=0

              Show
              Kristina Taylor (Inactive) added a comment - - edited For the analysis we need to do the following: Determine which tables are candidates for the change Analyze how tables are used and which tables will be deprecated for KRAD Ask Jerry to confirm results I started an analysis document: https://docs.google.com/a/kuali.org/spreadsheet/ccc?key=0AqGzZp-mOGfNdEdSUzdRYXVCa3BubkZ6eWxScEJtSUE#gid=0
              Hide
              Permalink
              Kristina Taylor (Inactive) added a comment - - edited

              Analysis Notes:

              1. In general, most tables are renamed from krns_ to krad_
              2. We can safely drop krns_doc_typ_attr_s as it is unused
              3. krns_lookup_rslt_s will remain the same as it is deprecated
              4. krns_lookup_rslt_t and krns_lookup_sel_t will remain the same as they are deprecated, but there are some accidental references in KRAD, so those need to be removed
              5. krns_sesn_doc_t will remain the same as it is deprecated, and the code will be removed as per KULRICE-10178

              Jerry has confirmed these results so we should be good to go on the implementation.

              Show
              Kristina Taylor (Inactive) added a comment - - edited Analysis Notes: In general, most tables are renamed from krns_ to krad_ We can safely drop krns_doc_typ_attr_s as it is unused krns_lookup_rslt_s will remain the same as it is deprecated krns_lookup_rslt_t and krns_lookup_sel_t will remain the same as they are deprecated, but there are some accidental references in KRAD, so those need to be removed krns_sesn_doc_t will remain the same as it is deprecated, and the code will be removed as per KULRICE-10178 Jerry has confirmed these results so we should be good to go on the implementation.
              Hide
              Permalink
              James Bennett added a comment -

              We're adding another table that goes along with the krns_nte_t and krns_att_t tables. It is named krns_att_cntnt_t and it will be used with an optional implementation of the attachment framework which will store attachments in the database instead of the filesystem (See KULRICE-12444).

              Show
              James Bennett added a comment - We're adding another table that goes along with the krns_nte_t and krns_att_t tables. It is named krns_att_cntnt_t and it will be used with an optional implementation of the attachment framework which will store attachments in the database instead of the filesystem (See KULRICE-12444 ).

                People

                • Assignee:
                  Kristina Taylor (Inactive)
                  Reporter:
                  Jerry Neal (Inactive)
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Time Tracking

                    Estimated:
                    Original Estimate - 2 days
                    2d
                    Remaining:
                    Remaining Estimate - 0 minutes
                    0m
                    Logged:
                    Time Spent - 2 hours Time Not Required
                    2h

                      Agile

                        Structure Helper Panel