Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    Unneeded(?) tableCode and columnCode in DSLoader Servlet's response

    Hi Isomorphic,

    please see this thread. Below is a response of my DSLoader Servlet (copied from the other thread):
    Code:
    isc.DataSource.create({
        allowAdvancedCriteria:true,
        operationBindings:[
            {
                operationType:"update"
            },
            {
                operationType:"add"
            },
            {
                operationType:"remove"
            }
        ],
        serverType:"sql",
        tableCode:"660e6a52e29a8fc1a48d84c7fa2ee3e2",
        ID:"MY_ID_FROM_THE_DS_XML",
        fields:[
            {
                hidden:true,
                columnCode:"3854361464b9a2c3832c47bd39cddf54",
                name:"TENANT_ID",
                type:"integer"
            },
            {
                hidden:true,
                columnCode:"8f635513ba0e5d43d77836ba57c23dad",
                name:"LEAD_ID",
                type:"integer"
            },
            {
                title:"Reseller",
                displayField:"RESELLER_NAME",
                columnCode:"753f5ffa2e1542d0f28d4eb4bcab25e8",
                name:"RESELLER_ID",
                type:"integer"
            },
            {
                hidden:true,
                columnCode:"2582ec59e97c6010032089b939c5ba6b",
                name:"RESELLER_NAME",
                length:30,
                escapeHTML:true,
                type:"text"
            },
            {
                columnCode:"a74ec9c5b6882f79e32a8fbd8da90c1b",
                name:"DISTANCE",
                type:"float"
            }
        ]
    })
    I'm am wondering why I am getting the tablecode / columncode in the result. I never use autoDeriveSchema in my .ds.xml (v9.1p_2014-08-11, Oracle database).
    I don't think I need them and they increase the uncompressed size of the result from 230kb to 280kb. Is there some setting that enables autoDeriveSchema by default?

    Thank you & Best regards,
    Blama
    Last edited by Blama; 18 Aug 2014, 14:13.

    #2
    If you have a normal DataSource and an autoDeriveSchema DataSource, and the underlying table for the autoDeriveSchema DataSource has a foreignKey to a column for the normal DataSource, the only way that linkup can occur is if there are columnCodes available for the normal DataSource too.

    If you never use autoDeriveSchema, you can turn the whole subsystem off via setting datasource.autoLinkFKs to false in server.properties.

    Note we don't try to automatically turn this subsystem off by, for example, detecting autoDeriveSchema is never used. That would require scanning all your application DataSources in advance, and would limit the power of DynamicDSGenerator.

    Comment

    Working...
    X