OracleTimestamp bugs in some Add.* methods

OracleTimestamp bugs in some Add.* methods

Postby jlholt » Thu 09 Nov 2006 15:53

If you execute the C# snippet at the bottom of this post, you'll see that, given the minimum timestamp for an Oracle Timestamp data type, the only methods that succeed are AddMonths and AddYears. Of course, if you execute the following SQL statement, you'll see that there's nothing wrong, say, with adding 1 day to the minimum timestamp:

select to_timestamp('-4712-01-01','syyyy-mm-dd') + 1 from dual;



OracleTimeStamp t = new OracleTimeStamp(-4712, 1, 1, 0, 0, 0, 0, OracleDbType.TimeStamp);
try
{
t.AddMilliseconds(1);
}
catch (Exception ex)
{
}
try
{
t.AddSeconds(1);
}
catch (Exception ex)
{
}
try
{
t.AddMinutes(1);
}
catch (Exception ex)
{
}
try
{
t.AddHours(1);
}
catch (Exception ex)
{
}
try
{
t.AddDays(1);
}
catch (Exception ex)
{
}
try
{
t.AddMonths(1);
}
catch (Exception ex)
{
}
try
{
t.AddYears(1);
}
jlholt
 
Posts: 3
Joined: Mon 24 Jul 2006 17:51

Postby Alexey » Fri 10 Nov 2006 07:48

We are investigating this problem. You will be notified on results as soon as possible.
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Postby Alexey » Tue 12 Dec 2006 08:46

The problem is fixed.
Look forward to the next build.
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Postby Alexey » Mon 18 Dec 2006 08:14

OraDirect .NET Data Provider 3.55 Released!
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43


Return to dotConnect for Oracle