Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Wed, 30 Nov 2016 15:06:58 +0000 (UTC)
From: "Andrew Mashenkov (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.13007472.1474853914000.401605.1480518418458@Atlassian.JIRA>
In-Reply-To: <JIRA.13007472.1474853914000@Atlassian.JIRA>
References: <JIRA.13007472.1474853914000@Atlassian.JIRA> <JIRA.13007472.1474853914701@arcas>
Subject: [jira] [Commented] (IGNITE-3964) SQL: implement support for table
 alias
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 30 Nov 2016 15:07:00 -0000


    [ https://issues.apache.org/jira/browse/IGNITE-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15708828#comment-15708828 ] 

Andrew Mashenkov commented on IGNITE-3964:
------------------------------------------

H2 does not support table aliases and it seems we can't overcome this.

[~kuaw26], did you mean a table alias support (that mean table is accessible by more than one name) or it would be enough to have a possibility to set custom table name? 
For now table name is generated automatically depending on entity instance type name and can not be customized.

> SQL: implement support for table alias
> --------------------------------------
>
>                 Key: IGNITE-3964
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3964
>             Project: Ignite
>          Issue Type: Task
>          Components: SQL
>    Affects Versions: 1.6
>            Reporter: Alexey Kuznetsov
>            Assignee: Andrew Mashenkov
>             Fix For: 2.0
>
>
> We have ability to specify aliases for columns via org.apache.ignite.cache.QueryEntity#getAliases.
> But how about alias for table name? This could be useful in case of moving legacy application to Ignite with a lot of SQL statements.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)