Howdy Alex
It is the same on the english forum board. There are just lots of folks
complaining about data loss from file corruption. I have had it happen
to me and it is fustrating. The latest couple of complaints go
something like this ' I spent two days transfering data frmo [usually
Access] to Base...and my data is gone', or 'I put in over 100 contacts
and....now it is gone', and when they say gone they mean gone. You
can't get a zip program to open these files, you can't get a zip repair
utility to repair them so you can open them. So what should someone do,
unwind it by hand?
The real problem is this. Base crashes and I do mean base because I
don't see people complaining like this for the other modules, in
unpredictable ways and that is the part that most concerns me. If you
can say don't do this or it will crash great. But you can't, it is a
case of do this one time and it dies, do it again and it is fine. Open
this window and move to fast with the mouse...dead.
Alex Thurgood wrote:
Le jeudi 19 janvier 2006 à 12:20 -0500, Andrew Jensen a écrit :
Hi Drew,
Would it be possible for someone to give me a brief -bullet item list of
when, or what events trigger, this write back to permanent storage. I
now have a copy of the 2.0.1 source code on my machine, so if you need
to refer me to specific modules for review as the best way to get this
information that is acceptable. I would then most likely come back with
specific questions from my review of the code.
Judging by the number of complaints I have seen on the French n-l user
lists about data loss through crashing, and as a voluntary QA member, I
would say that this is a very good topic for discussion, but that I am
hopelessly incompetent to respond. To be fair, it appears that Base has
become more stable in the current 2.0.1 version, but who wants to spend
hours constructing a database to have to rebuild everything when the app
regularly goes pear-shaped.?
I might be wrong as to how it functions, but my understanding is that as
long as the I/O stream is not written to disk in the ODB file, then
everything still resides in memory. From what I recall, one of the
challenges of embedding a db into an openoffice.org document was the
necessity to make the base i/o streamable. This was one reason given why
sqlite wasn't chosen, because it's i/o model wasn't streamable in a way
that could easily be embedded into an OOo document. Like I said, I'm not
technically competent to go any further than what I've read in the past
from various devs on different lists, so I may be completely off the
mark.
Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
|
