René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Feature Request: Improved [DBNull]::Value comparison","articleBody":"# Summary of the new feature/enhancement\r\n\r\nAs a PowerShell user, I expect some (many!) conveniences with regards to comparisons and type conversions.  [dbnull]::value has had some improvement recently with #9794 but could use improvements with other comparisons, e.g. `[dbnull]::value -gt 10` should _not_ error out, at least from my perspective.\r\n\r\nA practical example.  Let's say I have a CMDB with dbnull in a few spots I want to do comparisons:\r\n\r\n```powershell\r\n#Example scenario with a function that uses Invoke-Sqlcmd2 to pull data\r\n    Get-XXXXServer | Where-Object{$_.VCNumCPUs -gt 8}\r\n    #Error for every line where VCNumCPU has DBNull value\r\n\r\n    #workaround before recent dbnull handling fix\r\n    Get-XXXXServer | Where-Object{[string]$_.VCNumCPUs -and $_.VCNumCPUs -gt 8}\r\n```\r\n\r\nThere is precedence for this:  `$null -gt 10` is `$false`, and `10 -gt $null` is `$true`\r\n\r\nCheers!","author":{"url":"https://github.com/RamblingCookieMonster","@type":"Person","name":"RamblingCookieMonster"},"datePublished":"2019-08-21T19:02:11.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":6},"url":"https://github.com/10404/PowerShell/issues/10404"}