"Robert Treat" <xzilla(a)users.sourceforge.net>
wrote in message news:200609042159.08811.xzilla@users.sourceforge.net...
If your serious about this, your best bet (IMHO) is to
get a copy of the
code
from SVN and take at look at the changes made for PostgreSQL support and
then
go about making similar patches for sybase. Dont expect to just dump the
whole patch back to the devs though, you should probably aim toward
delivering incremental patches back, and on top of that make sure to test
your changes on mysql (and postgresql to be nice) to make sure you haven't
broken anything.
Hi Robert,
Thank you for your comments. I don't know mysql, postgresql, or oracle, but
I do know Sybase ASE. Since you mention using the postgres code, I'll assume
it is closest in syntax to Sybase T-SQL. Sybase has a free edition which
runs on Linux and can be used in production environments.
http://www.sybase.com/linuxpromo
There are limits, but it works for the Wiki I'd like to create.
I would appreciate your further comments on how challenging you think this
might be since I don't know the other DBMS products. You mention testing my
changes on them, but wouldn't my changes only be for the Sybase code?
Testing / Learning other DBMS's might be more than I can take on.
Regards,
Mark