Agree. The unsupported functions should be mentioned on the page that will 
cover Ignite ANSI-99 compliance. We have first results available for CORE 
features of the specification:
https://ggsystems.atlassian.net/wiki/spaces/GG/pages/45093646/ANSI+SQL+99 
<https://ggsystems.atlassian.net/wiki/spaces/GG/pages/45093646/ANSI+SQL+99>

That’s on my radar. I’ll take care of this.

—
Denis

> On Jan 23, 2018, at 10:31 AM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote:
> 
> I think we need a page listing the unsupported functions with explanation
> why, which is either it does not make sense in Ignite or is planned in
> future release.
> 
> Sergey, do you think you will be able to do it?
> 
> D.
> 
> On Tue, Jan 23, 2018 at 12:05 AM, Serge Puchnin <sergey.puch...@gmail.com>
> wrote:
> 
>> yes, the Cust function is supporting both Ignite and H2.
>> 
>> I've updated the documentation for next system functions:
>> CASEWHEN Function, CAST, CONVERT, TABLE
>> 
>> https://apacheignite-sql.readme.io/docs/system-functions
>> 
>> And for my mind, next functions aren't applicable for Ignite:
>> ARRAY_GET, ARRAY_LENGTH, ARRAY_CONTAINS, CSVREAD, CSVWRITE, DATABASE,
>> DATABASE_PATH, DISK_SPACE_USED, FILE_READ, FILE_WRITE, LINK_SCHEMA,
>> MEMORY_FREE, MEMORY_USED, LOCK_MODE, LOCK_TIMEOUT, READONLY, CURRVAL,
>> AUTOCOMMIT, CANCEL_SESSION, IDENTITY, NEXTVAL, ROWNUM, SCHEMA,
>> SCOPE_IDENTITY, SESSION_ID, SET, TRANSACTION_ID, TRUNCATE_VALUE, USER,
>> H2VERSION
>> 
>> Also an issue was created for review current documentation:
>> https://issues.apache.org/jira/browse/IGNITE-7496
>> 
>> --
>> BR,
>> Serge
>> 
>> 
>> 
>> --
>> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>> 

Reply via email to