Issue 119410 - CRASH - can not create ODB file with direct mysql connector extension - wizard and application crash
Summary: CRASH - can not create ODB file with direct mysql connector extension - wizar...
Status: CLOSED WONT_FIX
Alias: None
Product: Base
Classification: Application
Component: MySQL Connector/OOo (show other issues)
Version: 3.4.0 Beta (OOo)
Hardware: Mac Mac OS X 10
: P3 Normal (vote)
Target Milestone: ---
Assignee: dbaneedsconfirm
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-24 11:02 UTC by iplaw67
Modified: 2012-09-09 07:21 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Crash trace on Apple Mac OSX (51.99 KB, text/plain)
2012-05-24 11:03 UTC, iplaw67 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description iplaw67 2012-05-24 11:02:23 UTC 
AOO340m1

Mysql native connector extension available from extensions site.

Mac OSX 10.6.8 Snow Leopard

Since experiencing the crash with bug 119409, I attempted to create a new ODB file using a direct connection via the connector extension to a locally hosted mysql database, using the db creation wizard.


After entering the connection string :

localhost:3306/dbname

(which is a UI regression in itself, it used to be more user friendly than this I seem to recall, but will have to check)

I get to the window where it asks for ID/pwd combo. I enter the ID, tick the pwd box, enter the password, then spinning beach ball and the whole application crashes.

Trace enclosed. Regression over all previous versions OOo, and previous and actual versions of LO and NeoOffice.


Alex
Comment 1 iplaw67 2012-05-24 11:03:08 UTC 
Created attachment 77588 [details]
Crash trace on Apple Mac OSX
Comment 2 r4zoli 2012-05-24 11:09:37 UTC 
Mysql connector not developed after moving from Oracle to Apache, due to license incompatibilities. 
Use JDBC or ODBC connectors with MySQL on any platform.

Changed priority.
Comment 3 Oliver-Rainer Wittmann 2012-05-24 11:23:32 UTC 
We had fixed bug 118846 for AOO 3.4 - correct calling convention for ODBC on Windows.
May be this issue has the same root cause.

iplaw67@yahoo.co.uk:
Can you check, if the crash occurs with OOo 3.4 Beta?
If not, it would be an indicator that the above assumption might be correct.
Thanks in advance.
Comment 4 hdu@apache.org 2012-05-30 14:50:48 UTC 
*** Issue 119409 has been marked as a duplicate of this issue. ***
Comment 5 r4zoli 2012-09-09 07:20:59 UTC 
The MySQL native driver development moved to apache-extras:
http://code.google.com/a/apache-extras.org/p/aoo-my-sdbc/
due to license incompatibilities.


The bug will not fixed here. 

I submitted in new place an issue:
http://code.google.com/a/apache-extras.org/p/aoo-my-sdbc/issues/detail?id=4
Comment 6 r4zoli 2012-09-09 07:21:21 UTC 
wontfix-> closed