Re: [libreoffice-users] Re: Installing MySQL Connector

On 1.4.2012 20:27, Alexander Thurgood wrote:
> Le 08/02/12 20:02, Pertti Rönnberg a écrit :
>
> Hi Pertti,
>
>
> What exactly is the issue you have had with using the MySQL JDBC
> connector on Windows ?
>
> Documentation :
>
> Prerequisites : a JDK or JRE, access to a running mysql server instance,
> either locally or via the network (beware that internet connections to
> externally hosted mysql servers can be very slow, or access can be
> refused to them by hosting service companies for various security
> reasons). The user attempting to connect to the mysql server instance
> must have the rights to do so, and also any rights to create, modify ro
> change tables, table structures, etc, according to what is desired for
> that user. These must be configured in advance within the mysql server.
> A database schema (database name) must be created in advance of any
> attempt to connect via LO and the JDBC connector.
>
> A useful tool for this is phpmyadmin. This is included in XAMP for
> example, which contains a complete apache web server, mysql and php
> stack, obtainable here :
>
> http://www.apachefriends.org/fr/xampp-windows.html
>
>
> via JDBC: (These steps are only valid for the MySQL connector)
>
> Get the newest JDBC driver from
>
> http://www.mysql.com/downloads/connector/j/
>
> Start LibreOffice
>
> Goto Tools>  Options>  Java
>
> Press the browse button near "Classpath" and browse for the *.jar
> file(s) of your driver.
>
> The jar file is part of the zip file that you download from the mysql
> website. Look for the file called mysql-connector-java-5.1.18.jar
>
> Restart LibreOffice
>
> Open the data source administration dialog (Tools/Data Sources...) or
> start the database wizard.
>
> Press the button "New Data Source", in the name field, enter a valid
> name like "MySQL JDBC", and keep "JDBC" as type.
>
> Enter the data source URL
> mysql://host:3306/Nameofyourdatabase
>
> Switch to the tab page JDBC. Now you have to enter the driver class
> name. For the MySQL connector driver you have to insert:
>
> com.mysql.jdbc.Driver.
>
> You can test that the driver is loaded correctly by pressing the
> corresponding button. If the driver doesn't load, then there is either
> something wrong with your driver setup or your Java installation.
>
> Enter the name of the user you wish to connect, and mark the checkbox if
> this user needs a password.
>
> To be sure that your settings will be saved, press the Apply button.
>
> You can also test the connection by clicking on the appropriate button.
> If the connection fails, you will get an error message. If it succeeds,
> you will get a message telling you so.
>
> Save your ODB document with an appropriate name.
>
> Once saved, click on the Tables icon in the main Base window, the tables
> of your mysql database should appear (if you have defined any in advance).
>
>
>
> Alex
Hello Alex   (& LibO folks),
Thank you for asking and also for your kind instructions  - and I am 
sorry for my late reply.
No, there are no specific  issues, I just reacted to the discussions 
about connecting problems -- and a lot of other too, especially in 
version LibO3.5.x.
The reason to my reaction is that I appreciate very much the idea of 
having a free office suite like LibO and OpenO  but I am worried about 
the strategy of LibO's distribution.
In my vocabulary LibO-Base with it's embedded HSQLDB is a database 
program, a package like MSAccess with it's JET-engine. My knowledge of 
databases is limited to some 30 apps in MSAccess (VBA & macros, 
forms/subforms, reports, etc, but not SQL more than absolutely needed) 
almost 15 years ago, some of them quite demanding.  So, not interested 
in buying a new MSAccess for my need of 2-4 quite simple databases ( 
like an address book plus some date calculations, subforms, reports) nor 
to learn HTML/PHP languages or SQL, I read the introduction and 
installed LibO3.4.5 (on PC:Win7Prof/32B; on laptop: Win7Prem/64B) in 
early January this year. Believing that LibO-Base should be sufficient 
for my need.

I am sure LibO is a powerful package but I have not been able to find 
this out; I have never experienced a program causing that much problems
>>    from the very beginning I had problems first with the installing 
(no clear info about JRE) then with date calculations that did not work 
(the embedded HSQL is obviously an old not supported version), then 
wasting a lot of time and nerves trying to get Report Builder and 
creating Forms and Subforms in DesignView  work as promised in 
instructions -- they don't!
>>    LibO's Help (lifebuoy) opens to a lot of pages telling what 
different kind of help you can get, but it has not a single link to real 
immediate help. As an user I shall not be dependent of an ever so fine 
community's answers, I want to have the help immediately (see MSAccess, 
OpenO, etc). The LibO documentation and "getting started - Base" seem to 
be available only for those who know about them or who know where to 
look -- not for them who are new to the program. The only help of some 
quality is to be gotten in OpenO why I have had OpenO installed on a 
second laptop (Vista).
>>    when I install a program like LibO I do it because I have a need 
to do a job, something productive, with it; I must be entitled to trust 
in the program, that it works reliable. I must not spend hours-days 
solving out if it is me, my computer, the instructions or the program 
that fails. Neither am I interested in installing a new version every 
second week just to get new bugs and other problems to waste my time with .

I have been 'computerized' since early 1980 and have thus used a lot of 
different programs why I think I am quite a good representative for an  
ordinary user without skills in programming.
If there is a real goal to get ordinary people, newbies like me, to 
start using LibO -- not scaring us away -- then my recommendation is:

Stop developing LibO at a known stable version (e.g. LibO3.4.5) and 
start a thorough checking run to find out, fix and ensure that every 
detail and tool, instruction and function works as it is meant 
(promised) to, that the terms and references used are equal both in 
menus, toolbars and help
>>    if LibO-Base is meant to have a embedded db-engine then select 
one that is sufficient and up-to-date and is supported by a reasonable 
good documentation -- and is to be upgraded
>>    create a reliable connector (or link to one) that has sufficient 
instructions, that connects LibO to that db-engine without any kind of 
problems -- a connection that every newbie can manage
>>    all necessary info (install, JRE, get started, documentation) 
must be put on or at least have clear links to a collecting page (LibO's 
own home page) where all that guidance can be easily found and gives 
directly help
>>    the help must include clear enough basic step-by-step examples on 
how to do
When that version absolute certainly works perfect, then distribute it 
and continue with the developing from that controlled basis.

Just some examples:
>>    a subform created with the wizard does not recognize relationship 
made between the two forms
>>    "getting started with Base" tells how to create a form and a 
subform with the wizard but refers to a "database guide" for to create 
them in DesignView -- where is that db-guide?

A good idea when writing instructions, guides, manuals (etc.) is to let 
some no-experts not only read it but also practically follow the 
instructions to check if the info is understandable, logic and correct 
-- the expert author is too often forgetting that the remote reader may 
be a total novice.

All this is of course only my opinion based on my experiences.
I thank you all and wish LibreOffice and it's supporters and developers 
all the best.
Pertti Rönnberg

--
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