[
https://issues.apache.org/jira/browse/IGNITE-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943428#comment-14943428
]
Igor Sapego commented on IGNITE-1617:
-------------------------------------
String policy by classes is represented by the table below.
||Class||Current string policy||
|SqlQuery|std::string|
|TextQuery|std::string|
|Cache|char*|
|Portable|char* with std::string overloads|
|PortableStringArrayWriter|char* with std::string overloads|
|PortableStringArrayReader|char* with std::string overloads|
|PortableRawReader|char* with std::string overloads|
|PortableRawWriter|char* with std::string overloads|
|PortableReader|char* with std::string overloads but some args are only char*|
|PortableWriter|char* with std::string overloads but some args are only char*|
|PortableType|char*|
|Ignite|char*|
|IgniteJvmOption|char*|
|IgniteConfiguration|very dangerous usage of char*|
|IgniteError|char*|
|Ignition|char*|
> CPP: review string usage in public API
> ---------------------------------------
>
> Key: IGNITE-1617
> URL: https://issues.apache.org/jira/browse/IGNITE-1617
> Project: Ignite
> Issue Type: Task
> Affects Versions: 1.1.4
> Reporter: Igor Sapego
> Assignee: Igor Sapego
>
> Currently there is std::string type used in some parts of public API while
> const char* used in some other parts. Need to review API and suggest solution
> for the consistent string policy.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
