29 Aug
2006
29 Aug
'06
5:07 p.m.
I'm trying to convert a database to the 'new' schema used in the latest
OG version. When running wiki-toolkit-setupdb, I get the following message:
Upgrading: old_to_9
Grabbing and upgrading old data... read 333 nodes... read 1250
contents... done
However, when visiting the site, I still get the same error:
Database schema version 0 is too old (need 9) at lib/OpenGuides/Utils.pm
line 85
Anyone know why it's doing this?
Clair
29 Aug
29 Aug
5:14 p.m.
On Tue, 29 Aug 2006, Clair wrote:
I'm trying to convert a database to the
'new' schema used in the latest
OG version. When running wiki-toolkit-setupdb, I get the following
message:
Upgrading: old_to_9
Grabbing and upgrading old data... read 333 nodes... read 1250
contents... done
Hmm, it doesn't seem to be doing the next steps, where it drops the
tables. After that, it'll create the new versions (including the version
table), and then put all your data back
If it breaks on the permissions check, you ought to get an error reported
to you. Odd that you're not. However, that's my hunch - check that your
database user can create and drop tables
Nick
5:23 p.m.
Nick Burch wrote:
On Tue, 29 Aug 2006, Clair wrote:
Yep, the database user can do 'all'.
If it helps, the script I'm using is:
#!/usr/bin/perl
use CGI::Carp qw( fatalsToBrowser );
use Wiki::Toolkit
print "Content-type: text/plain\n\n";
system("wiki-toolkit-setupdb --type mysql --name [database] --user
[user] --pass [password]")
(as CGI)
I'm trying to convert a database to the
'new' schema used in the latest
OG version. When running wiki-toolkit-setupdb, I get the following
message:
Upgrading: old_to_9
Grabbing and upgrading old data... read 333 nodes... read 1250
contents... done
Hmm, it doesn't seem to be doing the next steps, where it drops the
tables. After that, it'll create the new versions (including the version
table), and then put all your data back
If it breaks on the permissions check, you ought to get an error reported
to you. Odd that you're not. However, that's my hunch - check that your
database user can create and drop tables
30 Aug
30 Aug
6:44 p.m.
On Tue, 29 Aug 2006, Clair wrote:
Can you check to see if a table dbtest exists?
The upgrade script tries to create one, then drop it, to ensure it has all
the permissions it needs. Since you upgrade is dying before it reports it
has the right permissions, that'll at least tell us how far it made it.
Nick
If it breaks
on the permissions check, you ought to get an error reported
to you. Odd that you're not. However, that's my hunch - check that your
database user can create and drop tables
Yep, the database user can do 'all'.
7:23 p.m.
Nick Burch wrote:
On Tue, 29 Aug 2006, Clair wrote:
Can you check to see if a table dbtest exists?
The upgrade script tries to create one, then drop it, to ensure it has all
the permissions it needs. Since you upgrade is dying before it reports it
has the right permissions, that'll at least tell us how far it made it.
Nick
Hmm, it exists, but then, it always had:
content
dbtest
internal_links
metadata
node
Clair
If it
breaks on the permissions check, you ought to get an error reported
to you. Odd that you're not. However, that's my hunch - check that your
database user can create and drop tables
Yep, the database user can do
'all'.
31 Aug
31 Aug
12:11 a.m.
On Wed, 30 Aug 2006, Clair wrote:
Hmm, it exists, but then, it always had:
content
dbtest
internal_links
metadata
node
Ah, that'll probably be it then. It tries to create dbtest, finds it
there, and barfs. (The svn version of wiki::toolkit will hopefully give a
better error in this case)
Can you try removing the dbtest table, and running it again?
Nick
12:31 a.m.
Nick Burch wrote:
On Wed, 30 Aug 2006, Clair wrote:
Ah yes, that solved it. At least it's going to be fixed :)
Thanks for all your help, Nick!
Clair
Hmm, it exists, but then, it always had:
content
dbtest
internal_links
metadata
node
Ah, that'll probably be it then. It tries to create dbtest, finds it
there, and barfs. (The svn version of wiki::toolkit will hopefully give a
better error in this case)
Can you try removing the dbtest table, and running it again?
6236
days inactive
6237
days old
openguides-dev@lists.openguides.org
6 comments
2 participants
participants (2)
-
Clair -
Nick Burch