Hi all
I have a Sybase solution which is all based locally on a local server and works perfectly properly and never had a problem. I recently (about 2 months ago) added a mysql server to the mix in order that the internal database system can monitor a remote mysql based web store and see incoming orders / subscribers etc. As soon as the server was added, my solution became buggy when trying to ‘import a solution’ I get a variety of errors when importing, “lost communication with server” was one I had this morning. This seems to be temporarily resolved by restarting the server. If I restart servoy server, it allows me to do the import. The server is: Servoy version R2 2.2.5-build 337, repository version 27
the mysql server is jdbc:mysql://xxx.xxx.xxx.xxx/dbname, driver is org.gjt.mm.mysql.Driver. The server machine is a G5 2.0Ghz DP with latest Java and 10.4.6 etc.
I’d be grateful for any help anyone can give with this…
Thanks
Bevil
             
            
              
              
              
            
            
           
          
            
            
              Try to download the last MySQL Connector/J from here: http://dev.mysql.com/downloads/connector/j/3.1.html
             
            
              
              
              
            
            
           
          
            
            
              Hi Nicola
I downloaded it and found that my own Servoy installation already has the newer Mysql driver (I vaguely remember updating it sometime) My customer’s server, which runs the Servoy Server, reports the driver as org.gjt.mm.mysql.Driver - which seems to be the driver for the updated Mysql driver (I could be wrong but thats what I gather from the documentation). What should it be?
Thanks
Bevil
             
            
              
              
              
            
            
           
          
            
            
              The official mysql driver is accessible by “com.mysql.jdbc.Driver” or you can just get rid of the driver that shipped with servoy and copy the latest one to the servoy drivers folder, then org.gjt.mm.mysql.Driver will point to the correct one, otherwise it will point to the default one.
             
            
              
              
              
            
            
           
          
            
            
              aha…
so even though the latest driver might be there it would be overridden by the older ‘default’ one?
Cool… I’ll try removing the old one.
Thanks Nicola
Bevil