[Building Sakai] 2x: Micorsoft Sql Server conversion scripts: plan to move from trunk to contrib (and remove from 2.8.x, 2.7.x)

[Jean-Francois Leveque]

Removal seems the best choice. Is there a point of keeping mssql scripts 
in 2.6?

Might be worth removing other mssql files elsewhere in the source.

There may be other unsupported DB files elsewhere.

What's the current status of DB2 and other DBs not supported by the 
community?

Cheers,

J-F

Steve Swinsburg a écrit :
> Is there any point in keeping them at all, even in contrib? They are so out of date and totally unsupported that moving them to contrib might give false hope.
> 
> According to a 2006 JIRA: https://jira.sakaiproject.org/browse/SAK-7002, Microsoft allegedly stated that they would be prepared to fund ongoing support - I'm not sure if that eventuated. Plus also it means that developers need access to a non-free proprietary database and a Windows environment, and considering our developer base, that would be too much of a resource requirement.
> 
> regards,
> Steve
> 
> 
> On 08/03/2011, at 5:12 AM, Anthony Whyte wrote:
> 
>> Barring objections I plan to move the 2.7 and 2.8 Microsoft SQL server conversion scripts from trunk to contrib as well as remove them from the 2.7.x and 2.8.x maintenance branches.  The reasons are as follows:
>>
>> 1.  The Sakai Community does not publicly support MS SQL server for the Sakai CLE.
>> 2.  Due to no. 1 Sakai CLE developers are under no obligation to maintain the MS SQL server conversion scripts and few choose to do so.
>> 3.  Also due to no. 1 the MS SQL conversions scripts are not tested by QA.
>> 4.  As a result of nos. 1-3 the existing MS SQL conversion scripts for both 2.7 and 2.8 are in an anemic condition when compared to the community-supported MySQL and Oracle conversion scripts (see comparison below).
>> 5.  Due to no. 4 anyone attempting to perform an upgrade of a MS SQL database when upgrading their Sakai CLE to 2.7 or 2.8 is doomed to failure.
>>
>> Leaving the MS SQL conversion scripts in place gives the impression that we support MS SQL server when currently we do not.  Given their existing state--incomplete, unsupported and not QA'd--they should be pushed to contrib (over even simply deleted) in order to eliminate any misconception that may arise from their presence in our production releases and maintenance branches.
>>
>> If you object to their removal, be prepared to state how you intend to both maintain and test the MS SQL conversion scripts for upcoming releases, including 2.8.0.
>>
>> Cheers,
>>
>> Anthony
>>
>>
>> Trunk:
>>
>> 2.7.0: https://source.sakaiproject.org/svn/reference/trunk/docs/conversion/sakai_2_7_0_mssql_conversion.sql
>> 2.8.0: https://source.sakaiproject.org/svn/reference/trunk/docs/conversion/sakai_2_8_0_mssql_conversion.sql
>>
>> Compare these to
>>
>> 2.7.0: https://source.sakaiproject.org/svn/reference/trunk/docs/conversion/sakai_2_7_0_mysql_conversion.sql
>> 2.7.0: https://source.sakaiproject.org/svn/reference/trunk/docs/conversion/sakai_2_7_0_oracle_conversion.sql
>>
>> 2.8.0: https://source.sakaiproject.org/svn/reference/trunk/docs/conversion/sakai_2_8_0_mysql_conversion.sql
>> 2.8.0: https://source.sakaiproject.org/svn/reference/trunk/docs/conversion/sakai_2_8_0_oracle_conversion.sql