You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2018/03/19 08:23:00 UTC
[jira] [Updated] (IGNITE-5422) CREATE TABLE command should support
all-key fields case
[ https://issues.apache.org/jira/browse/IGNITE-5422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov updated IGNITE-5422:
------------------------------------
Labels: sql-engine (was: usability)
> CREATE TABLE command should support all-key fields case
> -------------------------------------------------------
>
> Key: IGNITE-5422
> URL: https://issues.apache.org/jira/browse/IGNITE-5422
> Project: Ignite
> Issue Type: Task
> Components: sql
> Reporter: Vladimir Ozerov
> Assignee: Alexander Paschenko
> Priority: Major
> Labels: sql-engine
>
> Currently it is impossible to create a table containing only {{PRIMARY KEY}} columns:
> {code}
> CREATE TABLE PersonProject {
> person_id BIGINT,
> project_id BIGINT,
> PRIMARY KEY (person_id, project_id);
> };
> {code}
> The reason for this limitation is that we have nothing to be saved as cache value and {{null}} values are restricted because they are indistinguishable from removal.
> We should allow this case somehow. Possible solutions:
> 1) Save empty object of table type: {{IgniteBinary.builder("PersonProject").build()}}
> 2) Save {{false}} as it is done in Java in Map-to-Set conversion
> Note that DML processing should be adjusted accordingly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)