[
https://issues.apache.org/jira/browse/TAJO-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13869231#comment-13869231
]
Keuntae Park edited comment on TAJO-492 at 1/13/14 2:00 AM:
------------------------------------------------------------
I just checked all the reserved keywords of Tajo as a table name in PostgreSQL,
and found that following keywords are allowed as table name.
{noformat}
mydb=# \d
List of relations
Schema | Name | Type | Owner
--------+-----------+-------+--------
public | filter | table | ktpark
public | first | table | ktpark
public | format | table | ktpark
public | grouping | table | ktpark
public | hash | table | ktpark
public | index | table | ktpark
public | insert | table | ktpark
public | last | table | ktpark
public | list | table | ktpark
public | location | table | ktpark
public | max | table | ktpark
public | min | table | ktpark
public | national | table | ktpark
public | nullif | table | ktpark
public | overwrite | table | ktpark
public | precision | table | ktpark
public | range | table | ktpark
public | regexp | table | ktpark
public | rlike | table | ktpark
public | set | table | ktpark
public | sum | table | ktpark
public | unknown | table | ktpark
public | var_pop | table | ktpark
public | var_samp | table | ktpark
public | varying | table | ktpark
public | zone | table | ktpark
{noformat}
I also checked all the data type tokens (time is one of them) and results in
{noformat}
mydb=# \d
List of relations
Schema | Name | Type | Owner
--------+-------------+-------+--------
public | bigint | table | ktpark
public | bit | table | ktpark
public | blob | table | ktpark
public | bool | table | ktpark
public | boolean | table | ktpark
public | bytea | table | ktpark
public | char | table | ktpark
public | date | table | ktpark
public | decimal | table | ktpark
public | double | table | ktpark
public | float | table | ktpark
public | float4 | table | ktpark
public | float8 | table | ktpark
public | inet4 | table | ktpark
public | int | table | ktpark
public | int1 | table | ktpark
public | int2 | table | ktpark
public | int4 | table | ktpark
public | int8 | table | ktpark
public | integer | table | ktpark
public | nchar | table | ktpark
public | numeric | table | ktpark
public | nvarchar | table | ktpark
public | real | table | ktpark
public | smallint | table | ktpark
public | text | table | ktpark
public | time | table | ktpark
public | timestamp | table | ktpark
public | timestamptz | table | ktpark
public | timetz | table | ktpark
public | tinyint | table | ktpark
public | varbinary | table | ktpark
public | varbit | table | ktpark
public | varchar | table | ktpark
{noformat}
(Actually, only 'binary' is not allowed as a table name)
If no matter, I think it is better to move all the above to non-reserved.
Does it make sense ?
was (Author: sirpkt):
I just checked all the reserved keywords of Tajo as a table name in PostgreSQL,
and found that following keywords are allowed as table name.
{noformat}
mydb=# \d
List of relations
Schema | Name | Type | Owner
--------+-----------+-------+--------
public | filter | table | ktpark
public | first | table | ktpark
public | format | table | ktpark
public | grouping | table | ktpark
public | hash | table | ktpark
public | index | table | ktpark
public | insert | table | ktpark
public | last | table | ktpark
public | list | table | ktpark
public | location | table | ktpark
public | max | table | ktpark
public | min | table | ktpark
public | national | table | ktpark
public | nullif | table | ktpark
public | overwrite | table | ktpark
public | precision | table | ktpark
public | range | table | ktpark
public | regexp | table | ktpark
public | rlike | table | ktpark
public | set | table | ktpark
public | sum | table | ktpark
public | unknown | table | ktpark
public | var_pop | table | ktpark
public | var_samp | table | ktpark
public | varying | table | ktpark
public | zone | table | ktpark
{noformat}
I also checked all the data type tokens and results in
{noformat}
mydb=# \d
List of relations
Schema | Name | Type | Owner
--------+-------------+-------+--------
public | bigint | table | ktpark
public | bit | table | ktpark
public | blob | table | ktpark
public | bool | table | ktpark
public | boolean | table | ktpark
public | bytea | table | ktpark
public | char | table | ktpark
public | date | table | ktpark
public | decimal | table | ktpark
public | double | table | ktpark
public | float | table | ktpark
public | float4 | table | ktpark
public | float8 | table | ktpark
public | inet4 | table | ktpark
public | int | table | ktpark
public | int1 | table | ktpark
public | int2 | table | ktpark
public | int4 | table | ktpark
public | int8 | table | ktpark
public | integer | table | ktpark
public | nchar | table | ktpark
public | numeric | table | ktpark
public | nvarchar | table | ktpark
public | real | table | ktpark
public | smallint | table | ktpark
public | text | table | ktpark
public | time | table | ktpark
public | timestamp | table | ktpark
public | timestamptz | table | ktpark
public | timetz | table | ktpark
public | tinyint | table | ktpark
public | varbinary | table | ktpark
public | varbit | table | ktpark
public | varchar | table | ktpark
{noformat}
(Actually, only 'binary' is not allowed as a table name)
> Cannot create a table named `time`
> ----------------------------------
>
> Key: TAJO-492
> URL: https://issues.apache.org/jira/browse/TAJO-492
> Project: Tajo
> Issue Type: Bug
> Affects Versions: 0.8-incubating
> Reporter: Daniel Einspanjer
> Fix For: 0.8-incubating
>
>
> I'm trying to test out data coming from a MySQL datawarehouse. I'm not able
> to create one of the tables which has the name "time". Putting it in
> backquotes (or any other kind of quote) does not help.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
