Can't you module maintainers (ubuntu or debian) just simply release TWO modules php5-sybase and php5-mssql that work properly ?
Please abandon putting two different functionalities into one php5 module. It is confusing and inconsistent. In the past php developers had to use Module sybase_ct to connect to mssql servers (gaining only a small subset of the features mssql server supports), now its the other way around, you need to include php5-mssql to access Sybase ASE databases. Though with mssql now having priority we Sybase developers have even less features of the sybase connectivity than before, e.g. no Stored procedure support anymore. Please release a module php5-sybase that handles the sybase connectivity and php5-mssql that handles the mssql connectivity. Maybe to avoid naming conflicts, release a new version php5-sybaseASE that handles the connectivity to Sybase Adaptive Server Enterprise ASE and php5-mssql2008 that handles mssqlserver 2008 connectivity. Both should be backward compatible to other, older releases of the respective products. It has been true in the past that sybase and mssql server shared a common code base, a common api and a common transfer protocol. However this is no longer the case for at least 10 years. SO please stop the madness of releasing a common "Sybase / MS SQL Server module for php5". Where else should I add this Enhancement request? At ubuntu brainstorm? At debian.org somewhere? -- sybase_* functions missing in php5-sybase for hardy https://bugs.launchpad.net/bugs/240519 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
