We're Moving!

The Vertica Forum is moving to a new OpenText Analytics Database (Vertica) Community.

Join us there to post discussion topics, learn about

product releases, share tips, access the blog, and much more.

Create My New Community Account Now


Inconsistent behaviour between ADO.NET with Microsoft SQL Server and with Vertica — Vertica Forum

Inconsistent behaviour between ADO.NET with Microsoft SQL Server and with Vertica

CleanCoderCleanCoder
in General Discussion
I've identified two distinctions between SQL Server and Vertica ADO.NET implementations:
  1. Vertica returns a result for non-query statements as part of a batch; e.g. CREATE TABLE; INSERT ...; SELECT ...; -> 3 results in Vertica, 1 in SQL Server
  2. ColumnOrdinal in the schema table returned by VerticaDataReader.GetSchema() is one-based, versus zero-based in SQL Server (note that both implementations are compliant with the ADO.NET specification)
Can you confirm if these distinctions are intentional?  Both can be worked around, although the former takes more effort in complex batches.

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Format
SpoilerCodeQuote
Heading 2Heading 1
Emoji
:):D:(;):/:o:s:p:'(:|B):#:*<3o:)>:)
Url
Image
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file
Home • General DiscussionComment As ...