Skip to main content

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

  • October 24, 2013
  • 0 replies
  • 6 views
CleanCoder
Forum|alt.badge.img
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.

    Still scrolling?
    Ask a question
    Terms & ConditionsAccessibility statement