Azuredatastudio: ObjectExplorerNode.nodePath contains display information

Created on 6 Apr 2018  路  2Comments  路  Source: microsoft/azuredatastudio

SQL Operations Studio Version: 0.27.3

For a few node types (e.g. temporal tables, columns, indexes), the node path contains display information, which makes the use of the findNodes API less straightforward.

Example of node path

Actual

_localhost,1401/Databases/WideWorldImporters/Tables/Purchasing.Suppliers (System-Versioned)/Purchasing.Suppliers_Archive (History)/Columns/SupplierID (int, not null)_

Expected

_localhost,1401/Databases/WideWorldImporters/Tables/Purchasing.Suppliers/Purchasing.Suppliers_Archive/Columns/SupplierID_

Use of findNodes API

Actual

const nodes = await sqlops.objectexplorer.findNodes(
  connectionId,
  'Column',
  undefined,
  'SupplierID (int, not null)',
  'WideWorldImporters',
  ['Purchasing.Suppliers (System-Versioned)', 'Purchasing.Suppliers_Archive (History)']);

Expected

const nodes = await sqlops.objectexplorer.findNodes(
  connectionId,
  'Column',
  undefined,
  'SupplierID',
  'WideWorldImporters',
  ['Purchasing.Suppliers', 'Purchasing.Suppliers_Archive']);
Area - Data Explorer Bug

Most helpful comment

This bug has been fixed in our latest insiders release and should behave as expected now

All 2 comments

@MattIrv could you please take a look at this?

This bug has been fixed in our latest insiders release and should behave as expected now

Was this page helpful?
0 / 5 - 0 ratings