简体   繁体   English

将一部分json查询结果存储在powershell中的变量中

[英]Storing a part of a json query result in a variable in powershell

I have the following output from a json query and I am looking for a way to search though it and pull the value for the tvdbid(the number 72663) and store it in a variable. 我有一个json查询的以下输出,我正在寻找一种方法来搜索它并拉取tvdbid的值(数字72663)并将其存储在一个变量中。

In the example below you can see there are actually 2 results so I would like it to store the both in array. 在下面的示例中,您可以看到实际上有2个结果,因此我希望将它们存储在数组中。

I am running powershell 3 on my pc so any v3 specific stuff should be ok. 我在我的电脑上运行powershell 3所以任何v3特定的东西应该没问题。

Out put 出局

{
    "data": {
        "langid": 7, 
        "results": [
            {
                "first_aired": "2010-11-15", 
                "name": "Accused", 
                "tvdbid": 72663
            }, 
            {
                "first_aired": "2010-01-17", 
                "name": "Enzai: Falsely Accused", 
                "tvdbid": 135881
            }
        ]
    }, 
    "message": "", 
    "result": "success"
}

Using PS V3: 使用PS V3:

$json = @'
{
    "data": {
        "langid": 7, 
        "results": [
            {
                "first_aired": "2010-11-15", 
                 "name": "Accused", 
                "tvdbid": 72663
            }, 
            {
                "first_aired": "2010-01-17", 
                "name": "Enzai: Falsely Accused", 
                "tvdbid": 135881
            }
        ]
    }, 
    "message": "", 
    "result": "success"
}
'@

$psobj = ConvertFrom-Json $json
$psobj.data.results.tvdbid

 72663
 135881

Most of the time I use now the CmdLet given by @mjolinor, but I still use the following old fashion XML serialization in two cases : 大多数时候我现在使用@mjolinor给出的CmdLet,但在两种情况下我仍然使用以下旧时尚XML序列化:

1- When I must use PowerShell V2 1-当我必须使用PowerShell V2时

2- Even in PowerShell V3 when the json returned by a web service is very big the PowerShell V3 is sending an exception. 2-即使在PowerShell V3中,当Web服务返回json非常大时 ,PowerShell V3也会发送异常。

Add-Type -AssemblyName System.ServiceModel.Web, System.Runtime.Serialization
$utf8 = [System.Text.Encoding]::UTF8    

function Write-String

{
  PARAM([Parameter()]$stream,
        [Parameter(ValueFromPipeline=$true)]$string)

  PROCESS
  {
    $bytes = $utf8.GetBytes($string)
    $stream.Write( $bytes, 0, $bytes.Length )
  }  
}

function Convert-JsonToXml

{
  PARAM([Parameter(ValueFromPipeline=$true)][string[]]$json)

  BEGIN
  { 
    $mStream = New-Object System.IO.MemoryStream 
  }

  PROCESS
  {
    $json | Write-String -stream $mStream
  }

  END
  {
    $mStream.Position = 0
    try
    {
       $jsonReader = [System.Runtime.Serialization.Json.JsonReaderWriterFactory]::CreateJsonReader($mStream,[System.Xml.XmlDictionaryReaderQuotas]::Max)
       $xml = New-Object Xml.XmlDocument
       $xml.Load($jsonReader)
       $xml
    }
    finally
    {
       $jsonReader.Close()
       $mStream.Dispose()
    }
  }
}

function Convert-XmlToJson
{
  PARAM([Parameter(ValueFromPipeline=$true)][Xml]$xml)

  PROCESS
  {
    $mStream = New-Object System.IO.MemoryStream
    $jsonWriter = [System.Runtime.Serialization.Json.JsonReaderWriterFactory]::CreateJsonWriter($mStream)
    try
    {
      $xml.Save($jsonWriter)
      $bytes = $mStream.ToArray()
      [System.Text.Encoding]::UTF8.GetString($bytes,0,$bytes.Length)
    }
    finally
    {
      $jsonWriter.Close()
      $mStream.Dispose()
    }
  }
}

In your case this will give the following : 在您的情况下,这将给出以下内容:

$json = @'
{
  "data": {
    "langid": 7, 
    "results": [{
       "first_aired": "2010-11-15", 
        "name": "Accused", 
       "tvdbid": 72663
       }, 
       {
       "first_aired": "2010-01-17", 
       "name": "Enzai: Falsely Accused", 
       "tvdbid": 135881
       }]
  }, 
  "message": "", 
  "result": "success"
}
'@

$xmlOut = Convert-JsonToXml -json $json
($xmlOut.root.data.results).ChildNodes[0].tvdbid.InnerText
($xmlOut.root.data.results).ChildNodes[1].tvdbid.InnerText

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM