About 6 months ago we moved from postgresql to sapdb. We are primarily a freebsd house, but we run sapdb on Redhat.
I can completely understand why a freebsd port is not being worked on by the sapdb dev team. It's a business decision, I would probably do the same thing and work on what most people want or need. However, what about at least making a native odbc driver for freebsd? You see, without a native odbc driver for freebsd, we have very few options on how to connect to the server from any of our bsd boxes. Right now we use the perl DBI proxy, which works, is stable, and the performance is not too bad since it caches the connections. However, it is an uneasy feeling knowing that we have to hack in a workaround like that and have no other options. I would propose that spending the time to create a native freebsd odbc driver would up the chances of a lot more people using sapdb. It can't be nearly as much work as porting the whole source tree, and for the effort required to make a native odbc driver, it seems like in this case the rewards would more than justify the time and effort. We don't mind running the server on linux or solaris, that is not really a problem. The problem is being able to access the server from the rest of our applications, which of course cannot be ported themselves to the os that the db server runs on. Another proposal would possibly be for the sapdb team to provide some information on what would be the simplest approach for compiling just the libraries needed for the odbc driver. I'm guessing that a lot of the source tree would not have to be compiled just to create the odbc driver? Chris _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
