Re: horde-git-tools - base application db migration tables trouble
Luis Felipe Marzagao <[email protected]> Tue, 24 Oct 2017 07:11:20 -0200
| Newsgroups | gmane.comp.horde.devel |
|---|---|
| Message-ID | <[email protected]> |
Em 24/10/2017 06:15, Jan Schneider escreveu: > > Zitat von Luis Felipe Marzagao <[email protected]>: > >> Hello: >> >> After running "horde-git-tools git clone" and "horde-git-tools dev >> install", everything apparently went well. >> >> I could load horde configuration page via browser and set db >> configuration just fine and write it to base/config/cong.php by >> cliking save. >> >> Then, I ran horde-db-migrate (two times) and I ended up with: >> >> ubuntu@gittools:~/horde-src/base/bin$ ./horde-db-migrate >> [ INFO ] Migrating DB up. >> [ INFO ] Current imp schema version: 3 >> [ INFO ] Ending imp schema version: 3 >> [ INFO ] Current ingo schema version: 7 >> [ INFO ] Ending ingo schema version: 7 >> [ INFO ] Current sam schema version: 1 >> [ INFO ] Ending sam schema version: 1 >> [ INFO ] Current kronolith schema version: 27 >> [ INFO ] Ending kronolith schema version: 27 >> [ INFO ] Current turba schema version: 12 >> [ INFO ] Ending turba schema version: 12 >> [ INFO ] Current nag schema version: 17 >> [ INFO ] Ending nag schema version: 17 >> [ INFO ] Current mnemo schema version: 8 >> [ INFO ] Ending mnemo schema version: 8 >> [ INFO ] Current trean schema version: 5 >> [ INFO ] Ending trean schema version: 5 >> [ INFO ] Current ansel schema version: 14 >> [ INFO ] Ending ansel schema version: 14 >> [ INFO ] Current wicked schema version: 6 >> [ INFO ] Ending wicked schema version: 6 >> [ INFO ] Current whups schema version: 9 >> [ INFO ] Ending whups schema version: 9 >> [ INFO ] Current klutz schema version: 1 >> [ INFO ] Ending klutz schema version: 1 >> [ INFO ] Current jonah schema version: 4 >> [ INFO ] Ending jonah schema version: 4 >> [ INFO ] Current hermes schema version: 3 >> [ INFO ] Ending hermes schema version: 3 >> [ INFO ] Current sesha schema version: 2 >> [ INFO ] Ending sesha schema version: 2 >> [ INFO ] Current gollem schema version: 3 >> [ INFO ] Ending gollem schema version: 3 >> [ INFO ] Current agora schema version: 2 >> [ INFO ] Ending agora schema version: 2 >> [ INFO ] Current ulaform schema version: 3 >> [ INFO ] Ending ulaform schema version: 3 >> [ INFO ] Current vilma schema version: 3 >> [ INFO ] Ending vilma schema version: 3 >> [ INFO ] Current content schema version: 2 >> [ INFO ] Ending content schema version: 2 >> >> But I'm still getting "SQLSTATE[42S02]: Base table or view not found: >> 1146 Table 'horde.horde_prefs' doesn't exist" error when trying to >> navigate. >> >> Checking horde's db inside mysql, indeed there aren't any horde.* >> tables. >> >> I see now the git-source/base directory does not contain a >> "migration" folder. >> >> How should the base tables be created now? Should they be created >> automatically or am I skipping some step? >> >> Thanks a lot. > > Looks like the migration files of the Horde libraries cannot be found. > Does it work if you run the DB update from the configuration screen? > Ok, just found out. I was missing horde/Horde_Role and also the horde_dir setting in pear config. After installing and configuring it, horde-db-migrate has created Horde_* tables normally. I thought I wouldn't need to do that because the documentation from https://www.horde.org/development/git says: "If installing the framework libraries directly via PEAR, i.e. not with with the Horde Git Tools, you will need to define your horde application directory ..." Since I'm using horde-git-tools, I didn't run configure horde_role previously. Thanks. -- dev mailing list Frequently Asked Questions: http://wiki.horde.org/FAQ To unsubscribe, mail: [email protected]