Spatial (columns and other features) support for SQL server

We use lot of spatial features of SQL server. It seems like DataGrip doesn't  even understand the spatial column types yet.
It will be nice if DataGrip could understand and provide basic features like SSMS for spatial fields. I know you guys can do even better than basic SSMS!

Also I noticed, in a SQL Server procedure if you use custom types (we used custom table type). Datagrip doesn't recognize it.

7 comments
Comment actions Permalink

Hi,

You could track the progress of request similar to your description https://youtrack.jetbrains.com/issue/DBE-3616

As for SQL Server procedure, could you provide an example?

Thank you.

1
Comment actions Permalink

For example see below. GEOGRAPHY and GEOMETRY type are shown as "Unresolved object type".

I work with lot of spatial and SSMS too doesn't provide much support for it. But at least following would be nice.

  1. Recognition of base Spatial types with intellisense. Not marked as unresolved types.
  2. When displaying spatial types in tables, you can show something meaningful. See 2nd screenshot. It takes lot of space and provides no meaningful info. SSMS shows a visual representation of spatial in separate tab (Screenshot 3).
  3. Import/Export from spatial formats e.g. shape files.

I might be asking for too much and thus did not reply on bug. Maybe you guys already have thoughts around this and want to plan properly. Did not wanted to confuse the requirements on the bug!

I am sure JetBrains can do a lot better than those MS guys.

 RE@ custom types. I think my data-grip wasn't synchronised to understand the custom type i was using. Now it shoes it fine. Thanks.

 

 

0
Comment actions Permalink

Thank you for great example.

 

0
Comment actions Permalink

Hello @vasily - I found this by searching "datagrip sql server spatial" on Google - I'd also love to see recognition of spatial data types as a feature in Datagrip

0
Comment actions Permalink

DUMP. This is needed. 

0
Comment actions Permalink

I agree, this would be an awesome feature to have in DataGrip (and another reason to not use other subpar tooling) and sadly it doesn't seem to have made much traction in the 3+ years.

0
Comment actions Permalink

We need the same feature.
I think it should be develop and added to package faster.
Any plan yet?

0

Please sign in to leave a comment.