Posted: 25.04.2012, 16:57
ManoShu,
thats's no good sign. I'm forced to roleback this patch.
So what can we do to handle this part right? Either we can ask the Server for a Unique Value which identifies exactly the SQL Server 2008. then we need some additional Parameters to check the inherited classes if ObjectNames MUST be escaped.
Or the Microsoft-Documentations can help here to find out if there is a Connection-Paramter which we can send to force him to unescape such "_" chars right again. I know ProstgreSQL supports such options.
Hmm the null-values making me curious too. Can you find out something for me?
What happens here?
Statement.SetNull(I+1, ConvertDatasetToDbcType(Param.DataType))
Can you also try to send the Server a Query like Update Table1 Set Field1=1 Field2=NULL where ....;
Is this Statement valid?
Michael
thats's no good sign. I'm forced to roleback this patch.
So what can we do to handle this part right? Either we can ask the Server for a Unique Value which identifies exactly the SQL Server 2008. then we need some additional Parameters to check the inherited classes if ObjectNames MUST be escaped.
Or the Microsoft-Documentations can help here to find out if there is a Connection-Paramter which we can send to force him to unescape such "_" chars right again. I know ProstgreSQL supports such options.
Hmm the null-values making me curious too. Can you find out something for me?
What happens here?
Statement.SetNull(I+1, ConvertDatasetToDbcType(Param.DataType))
Can you also try to send the Server a Query like Update Table1 Set Field1=1 Field2=NULL where ....;
Is this Statement valid?
Michael