Difference between revisions of "OpenDBX/Future"

From Linuxnetworks
Jump to: navigation, search
(windows support)
(Windows support)
Line 3: Line 3:
 
== Windows support ==
 
== Windows support ==
  
One of the highest priority is supporting windows natively. Unfortunately, I'm not a Windows developer and even if many other people also want a Windows version, none had the time/knowledge to finish the job yet.
+
One of the highest priority is supporting the Windows platform natively using Microsofts "Services for Unix". Unfortunately, I'm not a Windows developer and even if many other people also want a Windows version, none had the time/knowledge to finish the job yet.
  
Anyway, the good news is: The library is prepared to deal with loading backends dynamically in a Windows-specific way. This code part needs some testing and we need a project file for MSVC - that should be all.
+
Anyway, the good news is: The library is already capable loading backends dynamically in a Windows-specific way and it was tested using Cygwin and MinGW. We need a Makefile and maybe a project file for MSVC - that should be all.
 
+
In the meantime, compiling OpenDBX using the Cygwin environment might already work.
+
  
 
== Version 1.5 ==
 
== Version 1.5 ==

Revision as of 00:08, 13 June 2008

This page should give you a rough impression about the next steps in the development of the OpenDBX database access library. Further suggestions are always welcome.

Windows support

One of the highest priority is supporting the Windows platform natively using Microsofts "Services for Unix". Unfortunately, I'm not a Windows developer and even if many other people also want a Windows version, none had the time/knowledge to finish the job yet.

Anyway, the good news is: The library is already capable loading backends dynamically in a Windows-specific way and it was tested using Cygwin and MinGW. We need a Makefile and maybe a project file for MSVC - that should be all.

Version 1.5

  • Prepared statement interface
  • DB2 backend

Version 1.7

  • Ingres backend
  • Informix backend

Version 2.0

  • Remove deprecated functions and constants
  • Use negative error constants
  • Use enums instead of preprocessor constants for all parameters and return values



Back to Overview