[fdo-trac] #285: FDO Causing MapGuide 2.0 to Crash MySQL based?

[FDO]

#285: FDO Causing MapGuide 2.0 to Crash MySQL based?
---------------------+------------------------------------------------------
 Reporter:  Rothgar  |         Owner:  gregboone
     Type:  defect   |        Status:  new      
 Priority:  blocker  |     Milestone:  3.4.0    
Component:  FDO API  |       Version:  3.3.0    
 Severity:  1        |    Resolution:           
 Keywords:           |   External_id:           
---------------------+------------------------------------------------------
Comment (by MaksimS):

 This may be as well infamous MapGuide Server 1.2/2.0 instability - the
 very same thing happened to me as well, and I'm using: Microsoft SQL
 Server 2005 (managed datastore, MGE), Microsoft SQL Server 2000 (via ODBC,
 MGE), Oracle-based datastores (MGE), and MySQL Server (MGOS). I didn't had
 time to investigate whether it's up to the underlying FDO or MG itself,
 but both MGOS and MGE do crash here and there. It seems that MGOS
 stability improved in 2.0.1, so try getting a patch.

 As for the MySQL Server 5.0.22 _and higher_, you need to have installed
 libmySQL.dll version 5.0.22 on your client machine, in FDO's bin folder
 (or your running app folder referencing FDO libraries) adding it's path to
 the PATH system variable. You can find libmySQL.dll v5.0.22 in previous
 MySQL Server binary packs.

-- 
Ticket URL: <http://trac.osgeo.org/fdo/ticket/285#comment:6>
FDO <http://fdo.osgeo.org/>
Feature Data Objects