You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "Sandhya Sundaresan (JIRA)" <ji...@apache.org> on 2015/11/16 06:06:11 UTC

[jira] [Resolved] (TRAFODION-1603) LOB: Insert into volatile table with LOB columns crashes sqlci

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

Sandhya Sundaresan resolved TRAFODION-1603.
-------------------------------------------
    Resolution: Fixed

> LOB: Insert into volatile table with LOB columns crashes sqlci
> --------------------------------------------------------------
>
>                 Key: TRAFODION-1603
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-1603
>             Project: Apache Trafodion
>          Issue Type: Bug
>          Components: sql-exe
>    Affects Versions: 1.2-incubating
>            Reporter: Sandhya Sundaresan
>            Assignee: Sandhya Sundaresan
>
> Specifying a lob column in store by is probably not supported, but this error is currently not being caught at the create table time. As shown in the following execution output. Table t was created with the lob column c1 in store by. The ddl was successful. But the next insert statement returned a compiler internal error 2235 and a perplexing 4035 error.
> control query default TRAF_BLOB_AS_VARCHAR 'OFF';
> control query default TRAF_CLOB_AS_VARCHAR 'OFF';
> create schema mytest6;
> set schema mytest6;
> create table t (c1 blob not null not droppable, c2 clob not null not droppable) store by (c1);
> insert into table t values (stringtolob('column 1'), stringtolob('column 2'));
> drop table t cascade;
> drop schema mytest6 cascade;



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