sqlite属性db并获取{urn}/metadata/{guid}/属性似乎返回了一些不匹配的dbids（objectids）
我尝试获取具有特定属性的NavisWorks项目的dbids。
使用默认设置将NWD转换为SVF2。
当我查询属性db时，我的dbids与从{urn}/metadata/{guid}/properties endpoint返回的dbids不同。
查询结果：
相应的JSON数据：
[{
"objectid": 11,
"name": "3D Solid",
"externalId": "0/1/0",
"properties": {
"Neanex Connector": {
"ibcNAME": "Cone-1",
"ibcGUID": "6453c4c067d1476db9c68c4066e291c4"
}
}
},
{
"objectid": 2,
"name": "SomeSolids-1.nwd",
"externalId": "0",
"properties": {
"Neanex Connector": {
"ibcNAME": "SomeSolids-1",
"ibcGUID": "2613704afaeb4e68bcb1600a737df0b7"
}
}
},
{
"objectid": 27,
"name": "3D Solid",
"externalId": "1/5/0",
"properties": {
"Neanex Connector": {
"ibcNAME": "Wedge-2",
"ibcGUID": "25d5fb2daebe4a3fb3eb1c671012d5f3"
}
}
},
{
"objectid": 3,
"name": "SomeSolids-2.nwd",
"externalId": "1",
"properties": {
"Neanex Connector": {
"ibcNAME": "SomeSolids-2",
"ibcGUID": "425212b48a45457f9f9d5192e84bb0a4"
}
}
}]
摘要：
| SQLITE DBID | 外部ID | JSON | DBID指南 |
|---|---|---|---|
| 2 | 0 | 2 | 2613704AFAEB4E68BCB1600A737DF0B7 |
| 6 | 0/1/1/1/1/1/1/1/1 | 的 | “ |
| 27 | 与结果 | = | 45457F9F9D5192E84BB0A4 |
| 27 | 1/5/0 | 查询” | 25D5FB2DAEBE4A3FB3EB1C671012D5F3 |
哪些dbid是正确的？
为什么有区别？
关于
沃尔夫冈
I try to get the dbIds of Navisworks items which have a specific property.
The NWDs get translated to SVF2, using the default settings.
When I query the property DB, I get different dbIds than the dbIds that are returned from the {urn}/metadata/{guid}/properties endpoint.
Query with results:
Snippet of the corresponding json data:
[{
"objectid": 11,
"name": "3D Solid",
"externalId": "0/1/0",
"properties": {
"Neanex Connector": {
"ibcNAME": "Cone-1",
"ibcGUID": "6453c4c067d1476db9c68c4066e291c4"
}
}
},
{
"objectid": 2,
"name": "SomeSolids-1.nwd",
"externalId": "0",
"properties": {
"Neanex Connector": {
"ibcNAME": "SomeSolids-1",
"ibcGUID": "2613704afaeb4e68bcb1600a737df0b7"
}
}
},
{
"objectid": 27,
"name": "3D Solid",
"externalId": "1/5/0",
"properties": {
"Neanex Connector": {
"ibcNAME": "Wedge-2",
"ibcGUID": "25d5fb2daebe4a3fb3eb1c671012d5f3"
}
}
},
{
"objectid": 3,
"name": "SomeSolids-2.nwd",
"externalId": "1",
"properties": {
"Neanex Connector": {
"ibcNAME": "SomeSolids-2",
"ibcGUID": "425212b48a45457f9f9d5192e84bb0a4"
}
}
}]
Summary:
| SQLite dbId | External ID | json dbId | GUID |
|---|---|---|---|
| 2 | 0 | 2 | 2613704afaeb4e68bcb1600a737df0b7 |
| 6 | 0/1/0 | 11 | 6453c4c067d1476db9c68c4066e291c4 |
| 15 | 1 | 3 | 425212b48a45457f9f9d5192e84bb0a4 |
| 27 | 1/5/0 | 27 | 25d5fb2daebe4a3fb3eb1c671012d5f3 |
Which dbIds are the correct ones?
Why the differences?
Regards
Wolfgang
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
众所周知，SQLite DB中的dbids将是SVF dbids。如果要在转换为SVF2之后获得SVF dbids，则需要使用额外的标头
X-ADS-derivivative-Format：halldback来调用以下API。否则，您从属性API获得的objectid将是SVF2 dbids。As I know, the dbIds in SQLite DB will be svf dbIds. If you want to get svf dbIds after translating to svf2, you will need to call the below APIs with an extra header
x-ads-derivative-format: fallback. Otherwise, the objectIds you got from the properties API will be svf2 dbIds.两个至关重要的信息：
有“旧的” SVF dbids和更新的SVF2 dbids，请参阅：
Sqlite性质中的dbids db 始终'旧'''''svf dbids
使用标头
x-ads-derivivativative-Format 始终 'old'''''' SVF dbids。笔记：
如果您将此标头与一个导数（urn）一起使用，则只要您引用相同的衍生物，就必须在以下端点上始终如一地使用它。
Two crucial pieces of information:
There are 'old' SVF dbIds, and newer SVF2 dbIds, see:
The dbIds in the SQLite properties DB are always 'old' SVF dbIds
Using the header
x-ads-derivative-format: fallbackworks fine, and you always get the 'old' SVF dbIds.Note:
If you use this header with one derivative (URN), you must use it consistently across the following endpoints, whenever you reference the same derivative.