On Tue, 2009-07-28 at 07:26 -0400, Drew Jensen wrote: > Alex Thurgood wrote: > > Hi Drew, > > > > > > Trawling around on the OOo site and I found this : > > > > http://www.openoffice.org/issues/show_bug.cgi?id=79654 > > > > Guess it wasn't rated high enough priority. I also saw that Peter Eberlein > > posted on this list back in 2007 with the same problem relating to a PG > > server, where unfortunately the autoreconnect=true parameter didn't work > > for him...looks like we're a bit stuck... > > > > > > Well - didn't have much time to look at this yesterday and today is > going to be not much better.. > > But did get to try out the MySQL Native Connector: > > Using Client 2 (Win7) I connected to the same MySQL server and again > killed the connection in the background. > This time a nice error dialog pops up stating that "MySQL has gone away" > (MySQL's usual message). > > - at this point I realize that using the 3.2m_50 build is a real problem > here - as is 3.1. There is another bug, now fixed in the latest 3.2 > builds, where the dataview retrieves the data twice. The reason it comes > up here is that when you clear that error box under the native driver it > pops right back up, this is the second try for the data and which point > OO.o crashes....arrrgh. > > I'll try upgrading everything to the m_53 build, where the double access > bug is gone, tonight and start from there. > > Adios, > > Drew
Hey Drew, Any news on this connection issue with MySQL remote databases? It is driving us crazy here! Keith --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
