That was fast. You found a bug. Please test with latest version in the repository.
Thanks Oliver Am Friday 01 January 2016, 18:46:09 schrieb AP: > Dear All, > > > meanwhile I compiled QMS 1.5.1 following the tutorial > > https://bitbucket.org/maproom/qmapshack/src > > As mentioned before I created a mysql db "myname". > > I created a db in QMS with the same name by using the menue with mysql > instead sqlite. > > The db appears in QMS menue "data". > > But if I try to create a folder "Tours" , the folder do not appears in > the db in QMS. > > Using phpmyadmin I can see the db myname and the folder "Tours". > > What's wrong ? > > Kind regards > > Axel > > > > ------------------------------ Message: 3 Date: Thu, 31 Dec 2015 > 16:56:20 +0100 From: AP <[email protected]> Subject: Re: > [Qlandkartegt-users] Qlandkartegt-users Digest, Vol 84, Issue 8 To: > [email protected] Message-ID: > <[email protected]> Content-Type: text/plain; > charset=windows-1252; format=flowed Hallo Oliver, I'm not very fimilar > with mysql but would be glad to help a little bit. I created a db with > the name "myname" and can access it as a user. But I don't know how to > deal with it from QMS side. How can I use a mysql-db in QMS 5.5.1 in > Arch Linux ? Kind regards Axel Am 22.12.2015 um 15:09 schrieb Oliver > > Eichler: > >>> hi, > >>> > >>> there has been another change in the database that needs migration of > >>> the database. Please backup your database and report errors. > >>> > >>> As you might have noticed QMapShack is supporting MySql now. To use > >>> MySql you need a database server and a user login to that server. On the > >>> database sever you have to create a database by: > >>> > >>> create database myname; > >>> > >>> This will create the database with name "myname". In QMapShack's > >>> database setup dialog you have to use that name. > >>> > >>> The challenge with using a MySql server is having multiple instances of > >>> QMapShack using the same database. This will create conflicts when > >>> inserting/updating items from different instances. I spent quite some > >>> efforts to catch all these conflicts. But you never know. Thus if you > >>> experience some peculiar behaviour please report. > >>> > >>> > >>> The next step will be a mechanism to manually/automatically update the > >>> database tree and the workspace. > >>> > >>> > >>> It would be nice if enough users test and challenge that feature before > >>> the next release. > >>> > >>> Oliver > >>> > >>> ------------------------------------------------------------------------ > >>> ------ _______________________________________________ > >>> Qlandkartegt-users mailing list > >>> [email protected] > >>> https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users > > ---------------------------------------------------------------------------- > -- _______________________________________________ > Qlandkartegt-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users ------------------------------------------------------------------------------ _______________________________________________ Qlandkartegt-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
