Databases
StackOverflow2013
Postsdbo
POC# TimeSpan.Parse invalid format returns incorrect value instead of exception
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POC# TimeSpan.Parse invalid format returns incorrect value instead of exception
    primarykey
    data
    text
    <p>TimeSpan.Parse("23:00:00") returns 23 hours.</p> <p>TimeSpan.Parse("24:00:00") returns 24 days!</p> <p>I realize that I made a mistake in that the allowable range of hours is 0-23. But for minutes and seconds if you attempt to parse an out of range value you get an exception. In the case of hours with an out of range value, the parser incorrectly assumes you meant days instead of hours.</p> <p>Can someone explain this?</p> <p>This example here covers this very topic and indicates that <a href="http://msdn.microsoft.com/en-us/magazine/ee309881.aspx">http://msdn.microsoft.com/en-us/magazine/ee309881.aspx</a></p> <p>The same appears to be true about TryParse. I get 24 days despite the docs stating that the parse should fail.</p> <p><a href="http://msdn.microsoft.com/en-us/library/3z48198e">http://msdn.microsoft.com/en-us/library/3z48198e</a></p> <pre><code>// String to Parse TimeSpan // --------------- --------------------- // 0 00:00:00 // 14 14.00:00:00 // 1:2:3 01:02:03 // 0:0:0.250 00:00:00.2500000 // 10.20:30:40.50 10.20:30:40.5000000 // 99.23:59:59.9999999 99.23:59:59.9999999 // 0023:0059:0059.0099 23:59:59.0099000 // 23:0:0 23:00:00 // 24:0:0 Parse operation failed. // 0:59:0 00:59:00 // 0:60:0 Parse operation failed. // 0:0:59 00:00:59 // 0:0:60 Parse operation failed. // 10: Parse operation failed. // 10:0 10:00:00 // :10 Parse operation failed. // 0:10 00:10:00 // 10:20: Parse operation failed. // 10:20:0 10:20:00 // .123 Parse operation failed. // 0.12:00 12:00:00 // 10. Parse operation failed. // 10.12 Parse operation failed. // 10.12:00 10.12:00:00 </code></pre> <p>Did I find a bug or am I doing something wrong?</p> <p>EDIT: I've tested this in LinqPad and using a Console app in .NET4 on Windows 7 64bit.</p> <pre><code> var result = TimeSpan.Parse("24:00:00"); Console.WriteLine(result); result = TimeSpan.Parse("24:00:00", CultureInfo.InvariantCulture); Console.WriteLine(result); </code></pre> <p>This results in:</p> <pre><code>24.00:00:00 24.00:00:00 </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDan Bailiff
    1. USDan Bailiff
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POC# TimeSpan.Parse invalid format returns incorrect value instead of exception
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POC# TimeSpan.Parse invalid format returns incorrect value instead of exception
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POC# TimeSpan.Parse invalid format returns incorrect value instead of exception
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYou are comparing result of TryParse and Parse. The TimeSpan.Parse(String) method tries to parse string (parameter) by using each of the culture-specific formats for the current culture. So you are getting days.
      singulars
      1. POC# TimeSpan.Parse invalid format returns incorrect value instead of exception
      1. USRomil Kumar Jain
    2. COIt throws an exception for me. Maybe it's a culture thing? @Romil: `Parse` calls `TryParse` behind the scenes so they should have the same result.
      singulars
      1. POC# TimeSpan.Parse invalid format returns incorrect value instead of exception
      1. USRawling
    3. COThis reliably generates an OverflowException when I try it. Improve your question by documenting the .NET version, your culture and any overrides you may have applied in the Windows regional settings.
      singulars
      1. POC# TimeSpan.Parse invalid format returns incorrect value instead of exception
      1. USHans Passant
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload