Setting and Retrieving Data

元数据库数据的设置与获取
博客介绍了元数据库中数据的设置与获取方法。可通过调用SetData方法设置数据,该方法参数包含METADATA_RECORD结构。此结构也用于接收数据,调用GetData或EnumData方法时需传入其指针。GetAllData方法可从键中获取多个数据条目。
Platform SDK: Internet Information Services 5.1

Setting and Retrieving Data

You can set data in the metabase by calling the SetData method. This method takes as one of its parameters a METADATA_RECORD structure, which contains information about the data (its identifier, attributes, user type, data type, a pointer to the data, and so on). By setting values for the members of the METADATA_RECORD structure when it is passed as an input parameter to the SetData method, you can specify the type of and storage method for the data. For example, you can specify that the data be stored in a secure manner by setting the METADATA_SECURE flag in the structure's dwMDAttributes member.

In addition to specifying the data to be retrieved, the METADATA_RECORD structure is also used to receive data from the metabase. When you call the GetData or EnumData methods, you pass in a pointer to a METADATA_RECORD structure to specify the data to be retrieved, and to receive the data. Your program must allocate the buffer into which the data will be retrieved, and pass a pointer to it in the pbMDData member of the METADATA_RECORD structure.

The GetAllData method retrieves multiple data entries from a key. In this case, you can use parameters of the GetAllData method to specify the data to be retrieved, and provide a buffer where the method returns an array of METADATA_GETALL_RECORD structures.

Platform SDK Release: Janurary 2002
[HTTP] Request idempotency key: b78ff023-85a1-4538-a565-a2db7f5fe626 [HTTP] --> POST /session {"capabilities":{"firstMatch":[{}],"alwaysMatch":{"appium:automationName":"UiAutomator2","platformName":"Android","appium:unicodeKeyboard":true,"appium:resetKeyboard":true,"appium:noReset":true,"appium:newCommandTimeout":60,"appium:allowInsecure":"*"}}} [AppiumDriver@4905] Calling AppiumDriver.createSession() with args: [{"firstMatch":[{}],"alwaysMatch":{"appium:automationName":"UiAutomator2","platformName":"Android","appium:unicodeKeyboard":true,"appium:resetKeyboard":true,"appium:noReset":true,"appium:newCommandTimeout":60,"appium:allowInsecure":"*"}},{"firstMatch":[{}],"alwaysMatch":{"appium:automationName":"UiAutomator2","platformName":"Android","appium:unicodeKeyboard":true,"appium:resetKeyboard":true,"appium:noReset":true,"appium:newCommandTimeout":60,"appium:allowInsecure":"*"}},{"firstMatch":[{}],"alwaysMatch":{"appium:automationName":"UiAutomator2","platformName":"Android","appium:unicodeKeyboard":true,"appium:resetKeyboard":true,"appium:noReset":true,"appium:newCommandTimeout":60,"appium:allowInsecure":"*"}}] [AppiumDriver@4905] Event 'newSessionRequested' logged at 1757347590851 (00:06:30 GMT+0800 (中国标准时间)) [Appium] Attempting to find matching driver for automationName 'UiAutomator2' and platformName 'Android' [Appium] The 'uiautomator2' driver was installed and matched caps. [Appium] Will require it at C:\Users\luser\.appium\node_modules\appium-uiautomator2-driver [Appium] Requiring driver at C:\Users\luser\.appium\node_modules\appium-uiautomator2-driver\build\index.js [AppiumDriver@4905] Appium v3.0.1 creating new AndroidUiautomator2Driver (v5.0.0) session [AppiumDriver@4905] Checking BaseDriver versions for Appium and AndroidUiautomator2Driver [AppiumDriver@4905] Appium's BaseDriver version is 10.0.0 [AppiumDriver@4905] AndroidUiautomator2Driver's BaseDriver version is 10.0.0 [AppiumDriver@4905] Explicitly enabling insecure features for this session as per the server configuration: [AppiumDriver@4905] uiautomator2:adb_shell [AndroidUiautomator2Driver@7c26] [AndroidUiautomator2Driver@7c26] Creating session with W3C capabilities: { "alwaysMatch": { "platformName": "Android", "appium:automationName": "UiAutomator2", "appium:unicodeKeyboard": true, "appium:resetKeyboard": true, "appium:noReset": true, "appium:newCommandTimeout": 60, "appium:allowInsecure": "*" }, "firstMatch": [ {} ] } [AndroidUiautomator2Driver@7c26] The following provided capabilities were not recognized by this driver: [AndroidUiautomator2Driver@7c26] resetKeyboard [AndroidUiautomator2Driver@7c26] allowInsecure [5b179515][AndroidUiautomator2Driver@7c26] Session created with session id: 5b179515-2be2-4fc3-9ed6-22bf9492e2d4 [5b179515][ADB] Using 'adb.exe' from 'C:\Users\luser\AppData\Local\Android\Sdk\platform-tools\adb.exe' [5b179515][ADB] Running 'C:\Users\luser\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 start-server' [5b179515][AndroidUiautomator2Driver@7c26] Retrieving device list [5b179515][ADB] Trying to find connected Android devices [5b179515][ADB] Getting connected devices [5b179515][ADB] Connected devices: [{"udid":"6e110b79","state":"device"}] [5b179515][AndroidUiautomator2Driver@7c26] Using device: 6e110b79 [5b179515][ADB] Using 'adb.exe' from 'C:\Users\luser\AppData\Local\Android\Sdk\platform-tools\adb.exe' [5b179515][ADB] Running 'C:\Users\luser\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 start-server' [5b179515][ADB] Setting device id to 6e110b79 [5b179515][AndroidUiautomator2Driver@7c26] Neither 'app' nor 'appPackage' was set. Starting UiAutomator2 without the target application [5b179515][ADB] Running 'C:\Users\luser\AppData\Local\Android\Sdk\platform-tools\adb.exe -P 5037 -s 6e110b79 shell getprop ro.build.version.sdk'
最新发布
09-10
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值