Re: [libreoffice-users] Indexing for Search not working?

     You are right: because Base holds all the data in memory until 
shutdown, embedded HSQLDB  databases can loss data if shutdown is not 
done correctly. MySQL keeps the data stored within its installed folder. 
Base connects to the MySQL server which accesses the data. The same 
thing is true for you favorite MySQL replacement (Mariadb).

--Dan

On 10/18/2012 10:33 AM, Tom Davies wrote:
> Hi :)
> Dan, does that data-loss happen when you use MySql?  I thought it only 
> happened with the embedded HsqlDb?
> Regards from
> Tom :)
>
>     ------------------------------------------------------------------------
>     *From:* Dan Lewis <elderdanlewis@gmail.com>
>     *To:* users@global.libreoffice.org
>     *Sent:* Thursday, 18 October 2012, 15:04
>     *Subject:* Re: [libreoffice-users] Indexing for Search not working?
>
>         As far as Base is concerned, I have not been having any
>     problems with 3.4.6, 3.5.6, nor 3.6.2. (I just installed 3.6.3.2
>     which is a release candidate. For my personal databases I use the
>     most, I use MySQL as the backend with any of these LO Base
>     versions as the front end. I work with Base 3.6.3.2 for my
>     writing. This database is embedded and contains only sample data
>     (no important data contained in it). As far as JRE, I use 1.6.0_24
>     (openjdk). LO seems to prefer this.
>         I also use AOO 3.4.1 at times. It seems to prefer the Openjdk
>     1.7.0_07.
>         The main problem with Base is the potential for data loss when
>     the program is not shutdown properly. This can be avoided by
>     extracting the data from the database file and then use Base to
>     connect to the data. (The data files are extracted to a separate
>     folder.) Unfortunately, it does not improve the speed of Base.
>
>     --Dan
>
>     On 10/18/2012 07:15 AM, Pertti Rönnberg wrote:
>     > Tom,
>     > That info of yours is not only interesting but very important
>     for me as an user - and most certainly for others too.
>     > Unfortunately you add that "it is how you imagine it works"!
>     >
>     > Would it be possible that you check that with the board or the
>     devs themselves and then confirm it to us?
>     > If I were you I definitely would like to be sure about the
>     proceedings - (a) if such really has been settled or  (b) if not
>     settled?
>     >
>     > Some posts ago I asked what version is for the time being
>     considered the most reliable, especially regarding Base?
>     > -- and what version of JRE is in that version needed for Base
>     (if anymore needed)?
>     > I have read the release notes and got an picture but what is
>     your opinion?
>     > My version now is LibO3.4.6 on Win7Pro/32 and Win7/64.
>     > Pertti Rönnberg
>     >
>     >
>     > On 18.10.2012 12:41, Tom Davies wrote:
>     >> Hi :)
>     >> The upgrade from 3.5.x to 3.5.7 is extremely unlikely to cause
>     problems.  That 3rd digit is roughly like a "Service Pack" number,
>     but divide it by 2 because MS only does 3 SPs whereas LO does 6 or 7.
>     >>
>     >> The 3.x.7 aims at avoiding introducing new features!  New
>     features are mostly in the 3.6.x or being lined-up for the 3.7.0. 
>     The 3.5.7 is likely to just have fixes for any lingering problems
>     in the 3.5.6. Most of those fixes will be being merging into the
>     3.6.3 and .4.  At least that's how i imagine it works. Certainly
>     once that 3rd digit reaches .4 the branch seems a lot  more stable.
>     >>
>     >> Regards from
>     >> Tom :)
>     >> ________________________________
>     >>> From: anne-ology <laginnis@gmail.com <mailto:laginnis@gmail.com>>
>     >>> To: Dr. R. O Stapf <reinhold@stapf-online.com
>     <mailto:reinhold@stapf-online.com>>
>     >>> Cc: users@global.libreoffice.org
>     <mailto:users@global.libreoffice.org>
>     >>> Sent: Thursday, 18 October 2012, 2:31
>     >>> Subject: Re: [libreoffice-users] Indexing for Search not working?
>     >>>
>     >>>        and now we're 3  :-)
>     >>>
>     >>> On Wed, Oct 17, 2012 at 2:44 AM, Dr. R. O Stapf
>     >>> <reinhold@stapf-online.com
>     <mailto:reinhold@stapf-online.com>>wrote:
>     >>>
>     >>>> On 17.10.2012 16:07, Pertti Rönnberg wrote:
>     >>>>
>     >>>>> BRAVO Anne-Ology!!
>     >>>>> Exactly that message - only in other words -- I have
>     repeatedly tried to
>     >>>>> tell to the LibO-experts (devs) since January:
>     >>>>> they must take a brake in developing and take a certain
>     version (e.g.
>     >>>>> 3.4.xx) and make every module of the suite - Base included -
>     absolutely
>     >>>>> free of bugs and inconsistencies both in programming and the
>     instructions
>     >>>>> and especially the LibO-Help.
>     >>>>> Every feature shall have a clear explanation and a detailed
>     guiding
>     >>>>> how-to in the LibO-Help -- easily understood by any average
>     non-expert
>     >>>>> user.
>     >>>>>
>     >>>> I cannot agree more.
>     >>>> I started with 3.5.4 a few month ago and saw some problems
>     disappearing in
>     >>>>    3.5.5 and 3.5.6. Currently I am hesitating to upgrade to
>     3.5.7.
>     >>>> I hope the dev-team listens to Pertti's words.
>     >>>>
>     >>>>
>     >>> -- For unsubscribe instructions e-mail to:
>     users+help@global.libreoffice.org <mailto:help@global.libreoffice.org>
>     >>> Problems?
>     http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
>     >>> Posting guidelines + more:
>     http://wiki.documentfoundation.org/Netiquette
>     >>> List archive: http://listarchives.libreoffice.org/global/users/
>     >>> All messages sent to this list will be publicly archived and
>     cannot be deleted


--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted