Do you have a plan supports nvarchar?

Open
#30 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp, sql
Domain
databases

Research direction

Start by reviewing the issue's current lists of supported C and SQL data types and the repository's language-extension entry points. The issue is complete when nvarchar is supported consistently with the existing character and numeric types, with coverage for the relevant behavior; no specific files or tests are named.

Written by the indexing model from the issue text.

Description

Currently, the extension supports the following data types: SQL_C_SLONG, SQL_C_ULONG, SQL_C_SSHORT, SQL_C_USHORT, SQL_C_SBIGINT, SQL_C_UBIGINT, SQL_C_STINYINT, SQL_C_UTINYINT, SQL_C_BIT, SQL_C_FLOAT, SQL_C_DOUBLE, SQL_C_CHAR. It supports the following SQL data types: int, bigint, smallint, tinyint, real, float, bit, varchar(n).

Do you have a plan supports nvarchar?

Dominant language
C++
Stars
117
Forks
51
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/sql-server-language-extensions

All issues in microsoft/sql-server-language-extensions

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.