https://issues.apache.org/ooo/show_bug.cgi?id=119368
r4zoli <r4zoli@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|FIXED |INVALID
--- Comment #3 from r4zoli <r4zoli@apache.org> ---
You not provided enough information, the ODBC 5.1.11 connection worked for me.
In original post you not mentioned long table names, only crash, which I can
not reproduce, in my MySQL-AOO setup.
If I create this table (code from MySQL bugreport 65200), in JDBC connected
MySQL, the table crated:
CREATE TABLE `thisisaverylongtablename` (
`idthisisaverylongtablename` int(11) NOT NULL,
`thisisaverylongtablenamecol` varchar(45) DEFAULT NULL,
PRIMARY KEY (`idthisisaverylongtablename`)
);
If I connect to same database with ODBC 5.1.11 connection the AOO 3.4 crash.
The crash caused by ODBC driver, this is out of AOO responsibility.
I set the status to invalid.
--
You are receiving this mail because:
You are on the CC list for the bug.
|