[
https://issues.apache.org/jira/browse/IGNITE-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15708828#comment-15708828
]
Andrew Mashenkov edited comment on IGNITE-3964 at 11/30/16 3:07 PM:
--------------------------------------------------------------------
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. But it could be added easily.
was (Author: amashenkov):
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)
