Problem importing and publishing new BS

rocketman

I'll start by saying the earth hasn't stopped spinning - everything is backed up and my app is still running.

I have been developing a new major release of my app under a different name (Freeflight) whilst at the same time making minor tweaks and mods to the current release( DLGC)

Last night I imported FF into the DLGC Test space but when I came to test before publishing it didn't want to play. It came up with strange errors.

"Problem renaming table xxx_vendors table xxx_tugs already exists (neither of the two tables are related in any way.

I created an new blank BS and the import, test and publish all worked, and I got teh DLGC test site to work by specifying to use an empty database rather than existing data,

So I know I have the option of Deleting DLGC and creating a new DLGC then restoring the data EXCEPT THAT One of the mods in the new release was I renamed my aircraft file to be gliders and created a new file tugs and then created a new group called aircraft containing gliders and tugs (I did this because there wee signiicant differences in the rules relating to the flights of each type of aircraft)

There was also two files in DLGC - vendors and instantmessages - which I'd forgotten to add to Freeflight

So the problem as I see it is I can start over but my backup file will have a table called Aircraft which really needs to be in the new table gliders (we can discount tugs because it is empty)

Would it be a simple case of restoring the data, dropping the gliders table and renaming aircraft to gliders or will that internally screw up AwareIM

Ideally of course I'd like to get the publish to work from my current position and try to understand what went wrong so I can avoid any mistakes in the future.

It was v late last night but would be happy to retace my steps and provide precise error messages if it helps

ACDC

If you are not using the same BS name to develop a new version, one of the cardinal rules when developing a similar version is to keep one single core where you work from.

It sounds like you have forked into another version and now when you import into your existing version Aware is unable to match the databse.

(This could also happen if you have restored your database recently and the version does not match your existing version so aware is out of sync)

I have a number of versions of my product, but there is only one core so when I make changes on one BS I then import that one into the others so they are all in sync.

So when you started the new version, you should have imported your existing version into the new project which now becomes the core. At the same time no changes are allowed to your existing system or any other version ( If you make changes to any other system without mirroring the changes in the new system then you have forked and will get this problem)

If you stick to this rule , then when you are ready to update your existing version everything will work because aware remembers where it left off and once again your existing version now upgraded becomes the core

Unfortunately I find AwareIMs only downfall is not being able to develop and publish multiple versions from a single core which could be a developers nightmare if they are in this space... but then thats another discussion

rocketman

rocketman wrote
So the problem as I see it is I can start over but my backup file will have a table called Aircraft which really needs to be in the new table gliders (we can discount tugs because it is empty)

Would it be a simple case of restoring the data, dropping the gliders table and renaming aircraft to gliders or will that internally screw up AwareIM

Hi ACDC - thanks for the overview and the heads up on what not to do in the future. Have you any thoughts on how now to get from not publishable to published. Will my idea quoted above work or is this a support ticket job

rocketman

Phew !!!! Made it.

Turned out to be relatively painless in the end - if a little laborious.

Ended up

1) deleted corrupted BS
2) Created new BS with same name
3) Imported th FreeFlight BS into the new DLGC Test Space
4)Tested then published. At this point I had an empty test space with all the tables correctly created in MySQL and a similar in Basdb
4) Using MYSQLADMIN From here on in, Restored from last backup. At this point the restoration process put back the aircraft file and also overwrote some other tables removing some attributes that existed in the new BS but didn't in the backup copy
5) dropped the gliders BO (see first post)
6) Renamed Aircraft to gliders
7)worked through the tables recreating the lost fields (attributes)

For step 7 AwareIM proved quite helpful. After the first pass, I'd missed a few. After I'd restarted AwareIM and began to work through my app, AW threw up some non fatal errors informing me there were "Unknown columms - [column name] in table [Table name]

I was able to fix these on the fly without logging out of AW which was a real time saver

All is well with the world (apart from Libya, Japan, Afghanistan Bahrain, Poverty stricken African countries, the price of petrol in the UK............................ ad infinitum