I have 1.6.3 installed, and it works fine, but it does not provide reporting. I'm trying to upgrade to 1.7 for that reason, but there is an error when importing the database.
"Connecting to database 'testlink': OK!1054 - Unknown column 'upgrade_ts' in 'order clause' - SELECT* from db_version ORDER by upgrade_ts DESC LIMIT 1DAtabase ERROR:Unknown column 'upgrade_ts' in 'order clause'
This also seems to have a database under 1.6.2. How to go forward? Much of the data does not migrate, and I need to know how to correct this.
Great thanks, kind regards. but HELP!!
1.6.3 to 1.7 Installation problem
Moderators: Amaradana, TurboPT, TL Developers
please send me a mysql dump of your db to francisco.mancardi@gmail.com
Fman
Linc is also helping on this issue.
It seems clear that your efforts to support 1.6 are not continuing; however, in moving from 1.6 to 1.7, we're losing our database. 1.7 shows an "IMPORT" feature, but 1.6 has no commensurate EXPORT feature. Is there any way to dump the database to a CVS or XML file, so that we might save ourselves the rather unwieldy task of recreating the database?
As with most databases - regardless of structure - there exists such a possibility. We realize you have changed the schema for 1.7, but again, it would help tremendously to be able to export what remains usable.
I'd hate to think we are left without an option here, as we have a great deal of information contained in the previous release!
HELP! PLEASE! HELP!
and THANK YOU@!@
It seems clear that your efforts to support 1.6 are not continuing; however, in moving from 1.6 to 1.7, we're losing our database. 1.7 shows an "IMPORT" feature, but 1.6 has no commensurate EXPORT feature. Is there any way to dump the database to a CVS or XML file, so that we might save ourselves the rather unwieldy task of recreating the database?
As with most databases - regardless of structure - there exists such a possibility. We realize you have changed the schema for 1.7, but again, it would help tremendously to be able to export what remains usable.
I'd hate to think we are left without an option here, as we have a great deal of information contained in the previous release!
HELP! PLEASE! HELP!
and THANK YOU@!@
I guess that something wrong happens during your migration process. Is not possible that you modified 1.6 DB schema?
There are still open some migration issues in our tracker ... (send reminder for your one).
But I believe that most of them is already solved in 1.7.1 . Did you use automatic migration for 1.7.0 or 1.7.1?
There are still open some migration issues in our tracker ... (send reminder for your one).
But I believe that most of them is already solved in 1.7.1 . Did you use automatic migration for 1.7.0 or 1.7.1?
Well, I can't believe I'm posting this, but I've had a tremendously difficult time upgrading from 1.6.2 -> 1.7.2. I have attempted upgrades upon upgrades, manually, automatic... You name it, I've done it. The absolute best that has happened is that 25MB of testcases now do NOT have test titles! Apparently, all of the node information was correct (and transferred/migrated), but the test titles did not translate/migrate over. I can't think that I've done anything wrong, because I've read all of the migration documents and [countless!] posts on the subject, so it would "appear" that I've followed the correct steps, but with a very untimely output. Mind you, I have NOT touched any of the databases in any way (just did the upgrades as instructed)...
Has anyone else seen this type of result? Unfortunately, I am faced with the nightmarish task of writing some kind of script that will take the test case titles out of a 1.6.2 database and put them into a 1.7.2 database. I have actually gotten to the point of writing a pseudo code translation, (ick!)...
Not happy about that...
<- People after me...
(and hoping that this is a bug, otherwise, I've done something really wrong a bunch of times)...
Has anyone else seen this type of result? Unfortunately, I am faced with the nightmarish task of writing some kind of script that will take the test case titles out of a 1.6.2 database and put them into a 1.7.2 database. I have actually gotten to the point of writing a pseudo code translation, (ick!)...
Not happy about that...
<- People after me...(and hoping that this is a bug, otherwise, I've done something really wrong a bunch of times)...
Go to mantis:
http://www.testlink.org/mantis/view.php?id=1328
I've posted the fix for the missing title problem, early this morning.
Please try it and let me know
http://www.testlink.org/mantis/view.php?id=1328
I've posted the fix for the missing title problem, early this morning.
Please try it and let me know