[sql] Industrial SQL Connector needs tweaks to connect to MSSQL

[GoogleCodeExporter]

Cloned from: 291795: [sql] Industrial SQL Connector needs tweaks to connect to 
MSSQL
https://bugs.eclipse.org/bugs/show_bug.cgi?id=291795

My aim is to set up a task management solution for a small developer team.
Based on the derby demo I implemented a mapping to a MS-SQL server database. I
also created a db schema like the one suggested in the demo. I get everything
to work with eclipse, but I discovered some drawbacks and I don't know if it is
my fault or just due to the beta state of the connector.

Here are my problems:

- bug_due is not set, when a new task is created
- it seems that the content assist for the user assignment does not get its
values from the shared DB
- when replying to a comment the string "null" is added in front of the quoted
text
- org.eclipse.mylyn.industrial.core.dto.IndustrialTask.modificationDate isn't
used at all (Is there a reason why?)

Here is the version information of the used software:
Eclipse 3.5.0
Mylyn 3.2.0
Industrial Connector 0.9.4
MS-SQL Server 2005

If it is needed, I can also post the db setup script and the configuration
files for the mapping.

Original issue reported on code.google.com by meijerf...@gmail.com on 27 May 2010 at 7:21

[GoogleCodeExporter]

Resolved some issues in release 0.9.5.v20091008

    >- bug_due is not set, when a new task is created

Is that bug due from the private fields, or the one in the attributes section? 
The first one doesn't seem to be accessible, since its private...

    >- it seems that the content assist for the user assignment does not get its
    >values from the shared DB

for this I have opened bug#291770

    >- when replying to a comment the string "null" is added in front of the quoted
    >text

This is caused by the framework not handling the null implementation in a 
robust way, it returns null instead of empty string and always adds \n

    >- org.eclipse.mylyn.industrial.core.dto.IndustrialTask.modificationDate isn't
    >used at all (Is there a reason why?)

This is just a r/o pass through parameter, to get auto update modified field 
from the database to the UI, so it has to be part of your query!

Original comment by meijerf...@gmail.com on 27 May 2010 at 7:26