Last night when I noticed that the qlandkarte database appeared to be an
sqlite3 database, I tried sqlite 3 "pragma integrity_check;" on the
database and it was corrupt. Next I tried dumping the database and then
building a new one from the dump, but that produced a database
with zero bytes in it.
So, I then started all over -- this time exiting qlandkarte after
every two or three gpx files and checking to see if the database is
corrupt. By the time I quit for the night, the database was up
to about 17MB and was still ok. Each time I added a gpx file,
the little icons showed up in front of all the items, so things
are looking better.
I never got any error messages from qlandkarte with the corrupted
database, so I had assumed everything should have been working and
I just was missing some concept.
I'm about half done and we'll see how it goes as I add the rest
of the gpx files a few at a time, exiting qlandkarte after each few.
It's looking like that should work ok.
I know of no way to produce the behavior aside from trying to do
all of them in one qlandkarte session, and that's a time consuming task.
Thanks for the response as I wasn't sure if name clashes or some other
thing could result in some data not making it into the database.
Harry
On 04/09/2014 12:29 AM, Oliver Eichler wrote:
> Hi Harry,
>
> I am not aware of a limit in that range. For example my database is 181MB.
> Probably there are limits at 2GB or 4GB.
>
> If you move large quantities of data in a single folder operations take quite
> a long time. The GUI is still responsive during that time. Thus several
> processes compete. That might result into a peculiar update of the GUI, like
> a missing icon. But items selected to be moved into the database should end
> up in the database unless the operation is aborted.
>
> If there are name clashes, or better to be said unique key clashes, you would
> get a database icon behind an item that is not intentionally in the database.
> However QLGT uses a timestamp and a counter to prevent that. Thus it's very
> unlikely or needs quite some manipulation to create identical keys.
>
> Is there a way to reproduce that behavior? I tried geocache pocket queries
> with 2500 points. It worked properly after the "add to database" operation
> finished, all waypoints had the database icon.
>
> Oliver
>
>> Gesendet: Dienstag, 08. April 2014 um 20:52 Uhr
>> Von: "Harry G McGavran Jr" <[email protected]>
>> An: qlandkarte <[email protected]>
>> Betreff: [Qlandkartegt-users] QlandkarteGT database question
>>
>> 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
>>
>
>
------------------------------------------------------------------------------
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
