![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Here is a question for those people out there using the Ingres .Net data provider. [quoted text clipped - 13 lines] You should be able to use the qualifier blankdate=null on the open statement, but there was a problem with this on earlier versions. Sorry I phrased that so poorly - you need to supply this information in the connection string. regards, Dominic |
#3
| |||
| |||
|
|
Here is a question for those people out there using the Ingres .Net data provider. I am trying to retrieve a date from an instance of a IngresDataReader using the GetDateTime method. The problem I have is this particular date column has blanks and for some reason the "GetDateTime" method substitues a blank with a default date of "01/01/1970". Just wondering if anyone else has overcome this problem and is able to load the blank date value. |
|
regards, Dominic -- Message posted via DBMonster.com http://www.dbmonster.com/Uwe/Forums....ngres/200603/1 |
#4
| |||
| |||
|
|
"Dominic Merrin via DBMonster.com" <u9483@uwe> wrote in message news:5cf99dcb67c2e (AT) uwe (DOT) .. Here is a question for those people out there using the Ingres .Net data provider. I am trying to retrieve a date from an instance of a IngresDataReader using the GetDateTime method. The problem I have is this particular date column has blanks and for some reason the "GetDateTime" method substitues a blank with a default date of "01/01/1970". Just wondering if anyone else has overcome this problem and is able to load the blank date value. You should be able to use the qualifier blankdate=null on the open statement, but there was a problem with this on earlier versions. |
| regards, Dominic -- Message posted via DBMonster.com http://www.dbmonster.com/Uwe/Forums....ngres/200603/1 |
#5
| |||
| |||
|
|
Thanks for that info Tom. [quoted text clipped - 4 lines] Guide and this is how the keyword is documented. The order of connection string components is not important is it? This keyword wasn't available until 3.0.2. If you started with an earlier version and upgraded, you might have run into a problem where the new .NET data provider didn't overwrite the old one. You might need to uninstall that component and reinstall it. All that said, I tried loading a dataset from an ingresDataAdapter and got the date 01/01/0001 (DateTime.Min) instead of the null I expected. If you are loading the value from a dataReader, you probably need to test the value for IsNull before trying to put it into a DateTime variable because the DateTime variable can't represent null. regards, [quoted text clipped - 12 lines] Dominic |
#6
| |||
| |||
|
|
Thanks for that info Tom. Have tried adding it to the connection string, but I get the error message "unknown connection string keyword 'blankdate'" Is this what you are talking about? I have referenced the R3 Connectivity Guide and this is how the keyword is documented. The order of connection string components is not important is it? |
|
regards, Dominic Tom M wrote: Here is a question for those people out there using the Ingres .Net data provider. [quoted text clipped - 13 lines] You should be able to use the qualifier blankdate=null on the open statement, but there was a problem with this on earlier versions. Sorry I phrased that so poorly - you need to supply this information in the connection string. regards, Dominic -- Message posted via http://www.dbmonster.com |
![]() |
| Thread Tools | |
| Display Modes | |
| |