The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
Upgrading Legacy groups...
Posted: 14 Aug 06 10:28 AM
|
fiogf49gjkf0d We are in the process of doing an upgrade from 5.2 to 6.2.4. As such, we would like to upgrade our groups to take advantage of new functionality in 6.2.4. Is there an easy way to do this? Just in playing around, I can copy and paste the group in manage plugins and it changes the company to our company name in 6.2.4, but doesn't appear to make any other changes to the group. Am I stuck recreating all of these from scratch? Any shortcuts that can be suggested?
Thanks in advance...cd |
|
|
|
Re: Upgrading Legacy groups...
Posted: 14 Aug 06 6:05 PM
|
fiogf49gjkf0d Groups weren't changed from Legacy, they're still the same basic structure. You can change the company name through a SQL statement in Administrator so there's really no need to do all of the steps you mentioned for each group.
|
|
|
|
Re: Upgrading Legacy groups...
Posted: 15 Aug 06 8:12 AM
|
fiogf49gjkf0d Interesting....the vendor we are using to assist us with this project told us that to take advantage of such things as the new way it handles locks on the data, as well as it not returning 10,000 results, but rather a subset until you scroll further down in the list, unless we rebuilt them in 6.2.4. Is there any additional insight on this?
Thanks in advance again...cd |
|
|
|
Re: Upgrading Legacy groups...
Posted: 15 Aug 06 12:29 PM
|
fiogf49gjkf0d There were changes made under the hood in 6.2.3 called VSS I believe, or virtual server side cursors. Groups now cache their data instead of keeping entire recordsets in memory and it does NOT require recreating a group for this to happen. It's all done by the client.
You may need to touch the SQL because there is certain conditions where the recordcount will return -1. Some say it is because of calculated fields being used and others say it's because the join types were wrong (the provider is looking for a specific type). It may actually be that both are the problem but I've yet to hear confirmation in a situation where someone used both calculated fields and the wrong join type. |
|
|
|
Re: Upgrading Legacy groups...
Posted: 15 Aug 06 2:18 PM
|
fiogf49gjkf0d So then if we just bring over our existing Legacy groups everything could be fine. In the unlikely event that one or both of those conditions exist, the group will throw an error and we can recreate it then...sound about right?
Of course best case is to have this all done in a test environment before going live...hehe...
Thanks again in advance...
cd |
|
|
|
Re: Upgrading Legacy groups...
Posted: 15 Aug 06 2:47 PM
|
fiogf49gjkf0d There's "Groups" and "Groups, ACO" types in Architect and after upgrading most of your types should be Groups, ACO (or at least mine are). The upgrade process should be converting the groups because there was no real difference that I noticed. What I did was upgrade a dev environment, make the SQL changes, bundle the group with their new projects and install the bundle. This creates a new pluginid and if you have to recreate them then you can at least make sure they work before putting them in officially. A test environment is definitely your friend in a situation like this. |
|
|
|
Re: Upgrading Legacy groups...
Posted: 15 Aug 06 2:53 PM
|
fiogf49gjkf0d So you did need to make SQL changes to your groups? Most of mine in the test/dev environment after upgrade are Groups, ACO. I haven't noticed any speed difference between the old and any new ones that I have created...They all seem to run the same...
cd |
|
|
|
Re: Upgrading Legacy groups...
Posted: 15 Aug 06 3:32 PM
|
fiogf49gjkf0d By SQL changes I meant plugin changes like from LEGACY to "Company Name", version 0 to version 1, etc. I changed it so that I could identify old plugins for removal. I didn't like having much Legacy stuff around after we upgraded. |
|
|
|