I have QLGT 1.7.6 running on Ubuntu 12.04 and am trying to get familiar with using the database. I've used QLGT on and off but never really tried using the database until now.
Things were going as expected from the tutorials and database stuff I've found, but with 510 gpx files and hundreds of tracks and more than 5000 waypoints in them, I started noticing something I don't understand with my limited knowledge of the database. At some point as my database was approaching about 22MB in size, I could clear my workspace, load several gpx files into the workspace. The workspace reflected exactly what was in the gpx files. I'd then right click on "workspace" to get the add to database function, select that function and pick a folder in my database. Generally, when doing that the little database icons would show up after each item in the workspace, indicating that those items had been added to the workspace and when I'd look in the database they'd be there. BUT, the problem is that somewhere as I approached the 22MB size, when I'd do this, some of the tracks and waypoints in the workspace would NOT get the little database icons when I'd select the add to database function as above. Even if I went ahead and tried to do the add to database and select a folder that already had some things in it, the things that got added or partially matched the things in the workspace with the little database icons. At least one track with a data base icon in the workspace didn't make it into the database, and another one without the icon in the workspace did make it in. I wondered if some of the problem was name collisions for tracks and waypoints, but when the database was smaller this seemed not to be in issue. I would have several items with the same name in a folder in the database and it seemed to work just fine. My main question is, under what circumstances should I expect some elements on the workspace not to get saved to the database when I in fact select them all to go to the database????? Harry ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ Qlandkartegt-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
