ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-5422) CREATE TABLE command should support all-key fields case
Date Mon, 04 Sep 2017 10:29:00 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-5422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vladimir Ozerov updated IGNITE-5422:
------------------------------------
    Labels: usability  (was: )

> 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
>              Labels: usability
>             Fix For: 2.3
>
>
> 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
(v6.4.14#64029)

Mime
View raw message