Sql-docs: STContains Red Squiggly When Checking a Polygon contained within Another

Created on 28 Jun 2019  路  9Comments  路  Source: MicrosoftDocs/sql-docs

I noticed that when using STContains on SSMS with SQL Server 2019

Not sure if this is an SSMS/SQL/etc. issue.

The function operates perfectly normal, but it always has a red squiggly with "Could not find method 'STContains' for type 'Microsoft.SqlServer.Types.SqlGeography' in assembly 'MicrosoftSqlServer.Types'.
on hover.

Here are Specs
SQL Server Management Studio 15.0.18131.0
Microsoft Analysis Services Client Tools 15.0.1347.0
Microsoft Data Access Components (MDAC) 10.0.18362.1
Microsoft MSXML 3.0 6.0
Microsoft Internet Explorer 9.11.18362.0
Microsoft .NET Framework 4.0.30319.42000
Operating System 10.0.18362

Pri3 assigned-to-author product-feedback sqprod

All 9 comments

@rayjohnson529 -- thank you for your feedback.

@MladjoA -- please look into this issue 2402.

@WilliamAntonRohm Ack.
@rayjohnson529 - thanks for reporting this. I have a repro and a new bug filed. We will keep you posted on progress.

Sadly there are many errors like this in SSMS :(
image
The result of an aggregate is never expected to be a geography, xml or any other non-comparable type, so SSMS gets confused and things it's an integer (which doesn't have methods obviously).

Is this a real scenario? I don't know. I use to use lag(...,0) over (order by (select 1)) as a means of caching computed LOB objects. Although with openjson and string_split I have less needs for these methods.

@MladjoA -- Mladen, please look into this aging issue 2402.

@MladjoA -- please add your new bug's path to this issue 2402.

@MladjoA Hi Mladen, we really need a link to your bug or fixed bug for this now aging GitHub Issue reported by the customer. Or can you please share any update info you have, in here by entering a Comment.
Thank you.

MladjoA returns from vacation next week, around 2019/Aug/07-08.

Issues Triagers, let's allow this aging Issue #2402 to remain open beyond the usual cut-off duration.

Sorry for delayed response, I was on a vacation.
As I mentioned previously we have a defect open for this, but I don't have ETA for fix yet.
Please let me know what else is needed.

Thanks,
Mladen

@MladjoA -- thank you for the update.

I am closing this issue now. You are welcome to @ mention me for any followup.
We hope to hear from you again.

Was this page helpful?
0 / 5 - 0 ratings