#904 Data not imported on upgrade

1.4
closed-fixed
nobody
None
1
2014-01-12
2013-12-03
turtle
No

Existing data and functionality should remain the same after an upgrade or it should be documented somewhere that this support will be dropped.
Ledgersmb Features or data columns from the database that are dropped or no longer supported could be documented.
Currently it seems the rewrite of the project and department system drops the project_id column from the parts table.

Discussion

  • Chris Travers

    Chris Travers - 2014-01-11

    Ok, trying to clarify this:

    What you are looking for is a list of db columns or data that is not imported, right?

    For the record, we don't "drop" data. Existing data is moved out of the way and imported into a new schema. This ensures that if something is omitted either by accident or design, it can be handled manually, looking at the old schema.

    Now the pre-upgrade fixes are applied to data before it is updated. However strictly speaking nothing is dropped.

    If you are upgrading from 1.2, your data will be in a schema called lsmb12, from 1.3, it will be lsmb13. From SQL-Ledger 2.8, it will be sl28.

     
  • Chris Travers

    Chris Travers - 2014-01-11
    • summary: Data silently dropped on upgrade --> Data not imported on upgrade
     
  • turtle

    turtle - 2014-01-11

    It is more of a ducumentation bug, it seems like the parts table in 1.2 has project_id's and I dont see them being imported to 1.4. I was just making a 'bug' to say it would be good to document when a column is dropped in a new version even in the comments of the upgrade sql file would be fine.

     
  • Chris Travers

    Chris Travers - 2014-01-12

    turtle, understood. I don't think we have decided how to handle lot or project mapping to business reporting unit. That's kind of a separate topic. This column was never actually used so it is likely that with other related changes (the move to the business unit system), this would have been not imported.

    There are a couple things that we could probably do a better job in documenting here. The first is the fact that project and department were replaced with business_unit and business_unit_class, and the second is in documenting upgrades for system integrators. I will look at getting this fixed today with new files in doc/

     
  • Chris Travers

    Chris Travers - 2014-01-12
    • status: open --> closed-fixed
     
  • Chris Travers

    Chris Travers - 2014-01-12

    basic notes are now in doc/db-changes, as of svn 6446

     

Log in to post a comment.

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

Sign up for the SourceForge newsletter:





No, thanks