when the embedded database grows, it starts having problems

moovida / beegis

Automatically exported from code.google.com/p/beegis

0 stars 0 forks source link

when the embedded database grows, it starts having problems #2

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

It seems that the embedded database starts having problems when growing in size 
and use.

Also it seems that if a database is used in regions far one from another, that 
helps to amplify the problems.

Original issue reported on code.google.com by andrea.a...@gmail.com on 9 Jun 2010 at 3:39

GoogleCodeExporter commented 9 years ago

Others set of test confirm that major problems came out mainly when the same 
database is used in regions far one from another.
The two mains problem are the freezing of GPS signal and the annotation that 
disappears after the drawing.

Original comment by mesca...@gmail.com on 14 Jun 2010 at 8:23

GoogleCodeExporter commented 9 years ago

OK, so summarizing, to reproduce it I should do something like:

1) create a db
2) activate the gps logging
3) zoom to an area A
4) insert gps geonotes, some annotations, create gps lines
5) do that for a bit
6) switch off gps
7) zoom to another area
8) do the same as in 4-5

Right?

Original comment by andrea.a...@gmail.com on 15 Jun 2010 at 7:25

Changed state: Accepted

GoogleCodeExporter commented 9 years ago

One more question. Do the databases that freeze contain imagery or documents? 
Migth there be a relation to that?

Original comment by andrea.a...@gmail.com on 15 Jun 2010 at 8:01

GoogleCodeExporter commented 9 years ago

I think that there isn't a strong relationship with imagery or documents: the 
problems came out also with only gps log and few annotations or geonote.

Original comment by mesca...@gmail.com on 15 Jun 2010 at 4:34

GoogleCodeExporter commented 9 years ago

yes, the procedure may be right, but I didn't do the same think step by step in 
the same session.
Usually I work for a whole (or for a part of) day in a area and a second day in 
a different area.

Original comment by mesca...@gmail.com on 15 Jun 2010 at 4:35

GoogleCodeExporter commented 9 years ago

Original comment by andrea.a...@gmail.com on 17 Jun 2010 at 5:40

Added labels: Priority-ARPA

GoogleCodeExporter commented 9 years ago

Luca, does this issue still apply with the new databases?
If yes, can you supply me with a database?
If no, can I close the issue?

Original comment by andrea.a...@gmail.com on 20 Aug 2010 at 12:33

GoogleCodeExporter commented 9 years ago

It seems that the problem persists also with new database (the last one I used 
is the 1.2M8 with the last beegis plugin).

I can try to search for an old database, or I can try to create a new one 
ad-hoc. In all my last survey I used a new database every time to bypass the 
freezing problem.

Currently I prefer to maintain this issue open.

Original comment by mesca...@gmail.com on 20 Aug 2010 at 5:00

GoogleCodeExporter commented 9 years ago

Can we close this issue? Do you still see that problem with the new database?

Original comment by andrea.a...@gmail.com on 27 Oct 2010 at 8:00

GoogleCodeExporter commented 9 years ago

Closing this for now. If the problem occurrs, we can reopen it.

Original comment by andrea.a...@gmail.com on 27 Oct 2010 at 11:42

Changed state: Fixed