Adding support for Microsoft SQL Server as a backend DB

[anonymous]

Requesting the inclusion of the Microsoft SQL Server 2000 database.

[anonymous]

See ticket #126 - future changes may allow you to integrate with MS SQL Server, or any other relational database (as a replacement for sqlite)

[henke.mike@…]

Any idea of this will be readdressed?

[anonymous]

Re-opened. not Duplicate since request for Microsoft SQL Server not MySQL, SQLite, or PostgreSQL

[anonymous]

I think you misunderstand #126. The point is, I don't think anyone wants to work on maintaining MSSQL support in the core (nevermind that it would require a copy of MSSQL). The Trac devs' hands are full enough as it is supporting SQLite, MySQL, and Postgres. So this is something that would probably be better off waiting on until there's more generic DB support (SQLAlchemy?)

Also, please be fair with priority, milestone, etc

[anonymous]

Hmm... Then I don't think this is a duplicate of #126 either. #126 is fixed and this is clearly not. Maybe close with won't fix. So at least people understands your intention without have to running arround and reopen the ticket.

Thanks!

[slide_o_mix at hotmail dot com]

I have a rough implementation of an MSSQL backend. I am coming up against some issues though.

For instance, several queries from trac use "LIMIT 1" SQL syntax which is not supported by MSSQL.

I am not quite sure what to do about those queries. There are some other schema things that I've run into as well (many of the DB fields are of type TEXT, but this doesn't work for primary keys or indices in MSSQL).

Any ideas would be appreciated.

[diroussel+trac@…]

slide_o_mix, the LIMIT issue can be worked around, but it's not as succinct as using LIMIT. You have to use TOP n.

See http://www.planet-source-code.com/vb/scripts/ShowCode.asp?txtCodeId=850&lngWId=5 for an example, you can probably find others too.

I'd be interested in you MS SQL port. You could put it on trac-hacks.org, there you'll get a project page and svn etc.

[diroussel+trac@…]

You can also use TOP.

SELECT TOP (10) * FROM TableA

[slide_o_mix at hotmail dot com]

I agree, that it can be worked around, the problem is that the trac api's use LIMIT in several places. I don't see a good way of abstracting whether to use LIMIT or TOP in those apis.