Early MSSQL Support
Brought to you by:
tuxmonkey
Menu
▾
▴
#47 Early MSSQL Support
I've put together some early support for MSSQL
backend. I was going to run IssueTracker on a box
that I already have that has some MSSQL DB's running
on it....
Since I developed this patch - I'm going to change
where I'm running IssueTracker & the DBI backend will
not be the same.
The patch: IssueTrack_404_MSSQL_Patch was developed to
add MSSQL DB interface to IssueTracker.
The release: issue-tracker-4.0.4 was used as the basis.
I was using a MSSQL 7.0 back end and the web interface
side of IssueTrcker was running on IIS 4.0 - running
on the same NT4.0 box (SBS4.5) - Old kit I know :o)
Refer to instructions for installing IssueTracker on a
windows platform. Pretty much worked as is for the
SBS4.5 setup. see...
http://sourceforge.net/forum/forum.php?
thread_id=1179192&forum_id=336969
You will need to add MSSQL support to PHP.
{There are plenty of references out there}
The main problem / difference with the MSSQL DBI is
that the "LIMIT" functionality within SQL statements
is not supported. I started to develop
a "query_limited" function within the DBI class to
bring the DB specific functionality down into the
module.
The bones of IssueTracker is working ok - except for
some problems that I've discovered when handling
single & double quotes, when submitting an issue.
{Didn't start to look into the cause}
I think that the approach I was taking to solve
the "LIMIT" issue needs a little more thought as -
"query()" is not the only interface into DBI
where "LIMIT" based queries are used.
To create the DB:
Generate yourselves a DB on the server using the GUI.
Set up the user / permissions, etc.
Then use: SQLCMD {or something similar} to generate
the DB schema - using the file: schema.mssql i.e.
SQLCMD -S <servername> -d <dbname> < schema.mssql
Use the same approach to setup the indexes & the data.
I've done a first pass - so I'll add this patch for
anyone else interested to take as a basis.
The patch in its current state WILL BREAK the other
DBI's, so it does need some more work.
MSSQL IssueTracker 4.0.4 DBI