trafodion-codereview mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sandhyasun <>
Subject [GitHub] incubator-trafodion pull request: Support for extracting lob to bu...
Date Tue, 05 Jan 2016 21:46:07 GMT
GitHub user sandhyasun opened a pull request:

    Support for extracting lob to buffer and buffertolob() function .JIRA : TRAFODION-1473

    *Support has been added to support new syntax that can extract to a user buffer.(Support
for extracting into a file already there)
    The new syntax looks as follows :
    extract from <table> (lob <lobhandle>, LOCATION <user buffer address as
long>, SIZE <user buffer address as long>
    Having the SIZE as an input/output allows the user to retrieve how much was actually extracted.
    For eg they could input a buffer of 1000 and SIZE 1000 but get back only 750 bytes of
    Although this syntax is going to be used mainly by jdbc applications and programs, to
test it via SQL interfaces (for developers only) a test driver has been added which gets built
as part of the build . The regression test executor/TEST130 has been enhanced to call the
testdriver to test this interface.
    *Support has been added to support reading from a user buffer into a lob.(Support for
reading from a string in memory or a file is already there)
    *Syntax :
    insert into <table> values (...,buffertolob(LOCATION <user buffer address>,
SIZE < sizeaddr>)
    update <table> set <lob column> = buffertolob(LOCATION <user buffer address>,
SIZE <sizeaddr>)
    *Added new Ansi datatypes -602 (SQLTYPECODE_BLOB) and -603(SQLTYPECODE_CLOB)
    *Added a clitestdriver( for dev use only) for easy testing and development of new interfaces
which could other be tested only via jdbc programs. 

You can merge this pull request into a Git repository by running:

    $ git pull lob_work_buffer

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #248
commit dd732847da86e2971766c5b169b0663093320e29
Author: Sandhya Sundaresan <>
Date:   2015-12-09T07:26:42Z

    Suppport for extractingl lob data to a user buffer inn a cursor-like fashion.
    Added a cli test interface to programmatically dynamic queries such as lob extract.

commit 5cfc9fa4e70eaeb041a03499fb2e7dd2fae7d28e
Author: Sandhya Sundaresan <>
Date:   2015-12-09T22:39:20Z

    Recommitting the last commit. Some files did notget added. Context/changes are the same
as earlier commit.

commit 353e1f3b8d619e5c5ee4934d6b58a6bf2b7aa542
Author: Sandhya Sundaresan <>
Date:   2015-12-09T22:42:23Z

    sqvers for clitestdriver

commit 781682afe4ee662e06e9e9da6b0753e4f3d9d673
Author: Sandhya Sundaresan <>
Date:   2015-12-11T19:25:39Z

    Changed output param for SIZE to be an input/output address.

commit e4f391f3dff713cf5b24c1e3860cfdc220a3a557
Author: Sandhya Sundaresan <>
Date:   2015-12-17T05:29:49Z

    Regression test for testing the programmatic interface for extracting lob data  into buffer
like a cursor.

commit 2ba37e8e1091f210a2640eef4ea614837a7f6f09
Author: Sandhya Sundaresan <>
Date:   2015-12-18T22:40:55Z

    Merge remote branch 'origin/master' into lob_work_buffer

commit 96ac8ebdb8b7df9f4da42352511a1c4411ada2bb
Author: Sandhya Sundaresan <>
Date:   2015-12-21T20:47:30Z

    More adjustments to lob regress test

commit 3fcf18813fd9f7b5ecce041b2675548e82f7e574
Author: Sandhya Sundaresan <>
Date:   2016-01-04T18:36:25Z

    insert/update LOB support from external user buffer

commit fd80e81f0435c091ee7f1e6a7bce320028abed03
Author: Sandhya Sundaresan <>
Date:   2016-01-05T18:04:41Z

    Additional fixes to deal with new Ansi blob datatype.

commit 13f897e8f6600138fd4a73594847a40faa328e40
Author: Sandhya Sundaresan <>
Date:   2016-01-05T21:42:39Z

    added copyrights to new testdriver files


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message