#2667 263 migration issue - maintain changelog reset to N?

closed-fixed
Migration (49)
5
2007-11-30
2007-10-23
ADAXA
No

In a system migrated to 263 on 17 September 2007 every table has had the 'maintain change log' flag set to 'N'.

Fortunately all ad_changelog records (and the iscustomization flag status) are preserved.

These table changes appears to be caused by migration because there are changelog records for 13 table IDs with the most recent changelog record dated 17 Sept but none since the migration.

There has been no reason for any user to go to each table and reset the flag.

regards..

Discussion

  • sboda

    sboda - 2007-10-30
    • assigned_to: nobody --> sboda
     
  • sboda

    sboda - 2007-10-30

    Logged In: YES
    user_id=1705860
    Originator: NO

    Reviewing

     
  • sboda

    sboda - 2007-10-30

    Logged In: YES
    user_id=1705860
    Originator: NO

    *** Reclassified as Bug ***

     
  • sboda

    sboda - 2007-10-30

    Logged In: YES
    user_id=1705860
    Originator: NO

    Replicated

     
  • sboda

    sboda - 2007-10-30
    • labels: --> Migration
    • assigned_to: sboda --> nobody
     
  • sboda

    sboda - 2007-11-30
    • assigned_to: nobody --> compiereqa
    • status: open --> open-fixed
     
  • sboda

    sboda - 2007-11-30

    Logged In: YES
    user_id=1705860
    Originator: NO

    Fixed and tested

     
  • sboda

    sboda - 2007-11-30
    • status: open-fixed --> closed-fixed
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks