BugNET

Open source issue tracking & project management

Forums

HomeHomeSupportSupportUpgrading BugNE...Upgrading BugNE...Upgrading 07.921 - confusedUpgrading 07.921 - confused
Previous
 
Next
New Post
3/20/2010 3:49 AM
 

Hi Davin,

I'd love to get my hands dirty with 08. But the upgrade of my existing data won't work. At one point you rename the tables, but I haven't found the bit of script that does that. So in a plain vanilla 07.921 the tables are not prefixed yet!

The RC 1 Schema.SqlDataProvider script starts with ALTER TABLE [dbo].[BugNet_IssueAttachments] DROP CONSTRAINT ... etc. This is the first script that is run and throws errors all over the place of course. I'm used to DNN style script distribution where you always stick to increments, but I figure you've taken an alternative route with this schema script which is supposed to fix all pre 0.8 dbs. I'm not sure how that works (because you need to account for all previous versions of BugNET), but I'll assume it's possible that way.

Where is the renaming happening? Which script should I run for the schema script to run correctly? Did I miss a post somewhere? I didn't spot it in the blog posts surrounding this, sorry.

Thanks,

Peter


Peter Donker
Bring2mind
DNN Document Management Solutions
 
New Post
3/20/2010 9:14 AM
 

Hey Peter,

The upgrades are done in incremental steps but I did take a little bit of a different approach for the upgrade from 0.7 -> 0.8.

First, I would upgrade your installation to the latest 0.7 version, 0.7.942.

Because the database changes were so significant in 0.8, it was actually a complete re-write of the DB tables and columns and I thought was too extensive to do alter table statements.

What the installation of 0.8 (RC1) will do is:

  1. Drops existing constraints and Installs the new tables using the BugNet.Schema.SqlDataProvider.sql script
  2. Runs the 0.8 (RC1) script - 0.8.140.0.SqlDataProvider.sql script which handles
    1. Migrating all data from old tables to new tables
    2. Inserting required data such as lookup tables and string resources
    3. Drops all old tables and constraints

Once this is done you can run the 0.8 RC2 install as you would a normal BugNET install, unzipping the files overtop and running install.aspx and it will execute the 0.8.167.0.SqlDataProvider.sql script.

The reason for the strict installation order is that the install engine doesn't handle getting the latest version from the database properly once it has been upgrade because the tables have changed. Something I am looking to fix for then next version and further simplifying the installation.

If you have any more questions please let me know.

Thanks


Davin Dubeau

follow us on twitter facebook users group google plus
 
New Post
3/21/2010 9:27 AM
 

Hey Davin,

Thanks. I got it. You're doing a migration by creating the new tables and filling them with the old data, after which you destroy the old data. OK, fair enough.

The next obstacle that has presented itself is the authentication. It turns out I've lost super user abilities. Retracing the code I see the standard roles are hard coded. So I've verified the existence of "Super Users" in BugNet_Roles and my userid guid bound to the role id in BugNet_UserRoles. Isn't that all there is to it? If so I'll dig deeper there to see if I can find the cause why IsInRole("Super Users") is not working.

Thanks,

Peter

BTW. I forgot to mention I'm a big fan of the project and love what you've built. I convinced multiple friends to adopt this. Cheers


Peter Donker
Bring2mind
DNN Document Management Solutions
 
Previous
 
Next
HomeHomeSupportSupportUpgrading BugNE...Upgrading BugNE...Upgrading 07.921 - confusedUpgrading 07.921 - confused


Forum Policy

These Discussion Forums are dedicated to the discussion of the BugNET issue tracker.

For the benefit of the community and to protect the integrity of the project, please observe the following posting guidelines:
1. No Advertising.
2. No Flaming or Trolling.
3. No Profanity, Racism, or Prejudice.
4. Site Moderators have the final word on approving/removing a thread or post or comment.
5. English language posting only, please.