Commerce Server Setup - Deploying a Package with Table Modifications

This is Interesting: Free IT Magazines  
Home > Archive > Commerce Server Setup > September 2005 > Deploying a Package with Table Modifications





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Deploying a Package with Table Modifications
Colin Bowern

2005-09-26, 6:00 pm

I added a few columns to the ShippingConfig table in the TransactionConfig
database. It seems with these modifications in place Site Packager is unable
to unpack this resource producing the following errors:

[11:59:38] GenericPuP: ImportTableDataFromXMLFile: Table=ShippingConfig:
Load XML Data file for table: ShippingConfig: 0x5E Invalid use of Null
[11:59:38] Error importing object data for Transaction Config from file C:\Documents
and Settings\xxxx\Local Settings\Temp\3\Transaction Config 5:Invalid procedure
call or argument

The underlying ShippingConfig.xml that is packaged in the site reflects all
of the proper columns but the database table was not created as such:

<xml xmlns:s='uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882'
xmlns:dt='uuid:C2F41010-65B3-11d1-A29F-00AA00C14882'
xmlns:rs='urn:schemas-microsoft-com:rowset'
xmlns:z='#RowsetSchema'>
<s:Schema id='RowsetSchema'>
<s:ElementType name='row' content='eltOnly' rs:updatable='true'>
<s:AttributeType name='shipping_method_id' rs:number='1' rs:writeunknown='true'
rs:basecatalog='MSCS_Store_TransactionCo
nfig'
rs:basetable='ShippingConfig' rs:basecolumn='shipping_method_id' rs:keycolumn='true'>
<s:datatype dt:type='uuid' dt:maxLength='16' rs:fixedlength='true' rs:maybenull='false'/>
</s:AttributeType>
<s:AttributeType name='shipping_method_name' rs:number='2' rs:nullable='true'
rs:writeunknown='true' rs:basecatalog='MSCS_Store_TransactionCo
nfig'
rs:basetable='ShippingConfig' rs:basecolumn='shipping_method_name'>
<s:datatype dt:type='string' dt:maxLength='255'/>
</s:AttributeType>
<s:AttributeType name='description' rs:number='3' rs:nullable='true' rs:writeunknown='true'
rs:basecatalog='MSCS_Store_TransactionCo
nfig'
rs:basetable='ShippingConfig' rs:basecolumn='description'>
<s:datatype dt:type='string' dt:maxLength='255'/>
</s:AttributeType>
<s:AttributeType name='action_page' rs:number='4' rs:nullable='true' rs:writeunknown='true'
rs:basecatalog='MSCS_Store_TransactionCo
nfig'
rs:basetable='ShippingConfig' rs:basecolumn='action_page'>
<s:datatype dt:type='string' dt:maxLength='255'/>
</s:AttributeType>
<s:AttributeType name='action_friendly_name' rs:number='5' rs:nullable='true'
rs:writeunknown='true' rs:basecatalog='MSCS_Store_TransactionCo
nfig'
rs:basetable='ShippingConfig' rs:basecolumn='action_friendly_name'>
<s:datatype dt:type='string' dt:maxLength='255'/>
</s:AttributeType>
<s:AttributeType name='progid' rs:number='6' rs:nullable='true' rs:writeunknown='true'
rs:basecatalog='MSCS_Store_TransactionCo
nfig'
rs:basetable='ShippingConfig' rs:basecolumn='progid'>
<s:datatype dt:type='string' rs:dbtype='str' dt:maxLength='255'/>
</s:AttributeType>
<s:AttributeType name='config' rs:number='7' rs:nullable='true' rs:writeunknown='true'
rs:basecatalog='MSCS_Store_TransactionCo
nfig'
rs:basetable='ShippingConfig' rs:basecolumn='config'>
<s:datatype dt:type='string' rs:dbtype='str' dt:maxLength='2147483647'
rs:long='true'/>
</s:AttributeType>
<s:AttributeType name='enabled' rs:number='8' rs:nullable='true' rs:writeunknown='true'
rs:basecatalog='MSCS_Store_TransactionCo
nfig'
rs:basetable='ShippingConfig' rs:basecolumn='enabled'>
<s:datatype dt:type='int' dt:maxLength='4' rs:precision='10' rs:fixedlength='true'/>
</s:AttributeType>
<s:AttributeType name='language_id' rs:number='9' rs:nullable='true' rs:writeunknown='true'
rs:basecatalog='MSCS_Store_TransactionCo
nfig'
rs:basetable='ShippingConfig' rs:basecolumn='language_id'>
<s:datatype dt:type='string' dt:maxLength='128'/>
</s:AttributeType>
<s:AttributeType name='shipping_method_type' rs:number='10' rs:nullable='true'
rs:writeunknown='true' rs:basecatalog='MSCS_Store_TransactionCo
nfig'
rs:basetable='ShippingConfig' rs:basecolumn='shipping_method_type'>
<s:datatype dt:type='string' rs:dbtype='str' dt:maxLength='20'/>
</s:AttributeType>
<s:AttributeType name='visible' rs:number='11' rs:nullable='true' rs:writeunknown='true'
rs:basecatalog='MSCS_Store_TransactionCo
nfig'
rs:basetable='ShippingConfig' rs:basecolumn='visible'>
<s:datatype dt:type='boolean' dt:maxLength='2' rs:fixedlength='true'/>
</s:AttributeType>
<s:AttributeType name='display_rank' rs:number='12' rs:nullable='true'
rs:writeunknown='true' rs:basecatalog='MSCS_Store_TransactionCo
nfig'
rs:basetable='ShippingConfig' rs:basecolumn='display_rank'>
<s:datatype dt:type='int' dt:maxLength='4' rs:precision='10' rs:fixedlength='true'/>
</s:AttributeType>
<s:AttributeType name='countries_supported' rs:number='13' rs:nullable='true'
rs:writeunknown='true' rs:basecatalog='MSCS_Store_TransactionCo
nfig'
rs:basetable='ShippingConfig' rs:basecolumn='countries_supported'>
<s:datatype dt:type='string' rs:dbtype='str' dt:maxLength='255'/>
</s:AttributeType>
<s:extends type='rs:rowbase'/>
</s:ElementType>
</s:Schema>
<rs:data>
<z:row shipping_method_id='{00000000-0000-0000-0000-002468008034}' shipping_method_name='Quick'
description='(7 to 10 business days)'
action_page='ChargeByQuantity_edit.asp' action_friendly_name='Charge by
Quantity' progid='commerce.stepwiseshipping'
config='<DICTIONARY xmlns:dt="uuid:304FB305-29A4-11d3-B0D4-00C04F8ED7A2"
version="1.0">
<DICTITEM key="mode"><VALUE dt:dt="i2">1</VALUE></DICTITEM>
</DICTIONARY>
' enabled='1' language_id='en-US' shipping_method_type='Ship' visible='True'
display_rank='1' countries_supported=''/>
</rs:data>
</xml>

Is there a recommended way of packaging a site with table modifications to
out-of-the-box tables?

Thanks,
Colin


Ravi Shankar

2005-09-26, 6:00 pm

Hi Colin,

The way to do this is as follows:

1. In the MSCS_Admin DB identify the Resource with which the
shipping_config table is associated (this is the value of the pup1
fieldname), Resources Table I think.
2. The pup2 fieldname value will give you the name of the scriptname that
creates this resource. Look up this field value in the pupdbscripts table
(the long text field contains the scripts for resource creation). If you use
the CommerceConfig PIA model you'll encounter the GetScript/PutScript
functions. The actual SQL scripts are avilable under the C:\Program
Files\Microsoft Commerce Server 2002\SDK\Site Create directory. Modify the
ShippingConfig table and use the PutScript to replace the script in the
MSCS_Admin DB for that site.
3. Pack the site. This time the default packager will extract the correct
script from the admin db and the data from your site db.

You would not have problems in unpacking the resource now. Let me know if
you want more information.
--
Ravi Shankar


"Colin Bowern" wrote:

> I added a few columns to the ShippingConfig table in the TransactionConfig
> database. It seems with these modifications in place Site Packager is unable
> to unpack this resource producing the following errors:
>
> [11:59:38] GenericPuP: ImportTableDataFromXMLFile: Table=ShippingConfig:
> Load XML Data file for table: ShippingConfig: 0x5E Invalid use of Null
> [11:59:38] Error importing object data for Transaction Config from file C:\Documents
> and Settings\xxxx\Local Settings\Temp\3\Transaction Config 5:Invalid procedure
> call or argument
>
> The underlying ShippingConfig.xml that is packaged in the site reflects all
> of the proper columns but the database table was not created as such:
>
> <xml xmlns:s='uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882'
> xmlns:dt='uuid:C2F41010-65B3-11d1-A29F-00AA00C14882'
> xmlns:rs='urn:schemas-microsoft-com:rowset'
> xmlns:z='#RowsetSchema'>
> <s:Schema id='RowsetSchema'>
> <s:ElementType name='row' content='eltOnly' rs:updatable='true'>
> <s:AttributeType name='shipping_method_id' rs:number='1' rs:writeunknown='true'
> rs:basecatalog='MSCS_Store_TransactionCo
nfig'
> rs:basetable='ShippingConfig' rs:basecolumn='shipping_method_id' rs:keycolumn='true'>
> <s:datatype dt:type='uuid' dt:maxLength='16' rs:fixedlength='true' rs:maybenull='false'/>
> </s:AttributeType>
> <s:AttributeType name='shipping_method_name' rs:number='2' rs:nullable='true'
> rs:writeunknown='true' rs:basecatalog='MSCS_Store_TransactionCo
nfig'
> rs:basetable='ShippingConfig' rs:basecolumn='shipping_method_name'>
> <s:datatype dt:type='string' dt:maxLength='255'/>
> </s:AttributeType>
> <s:AttributeType name='description' rs:number='3' rs:nullable='true' rs:writeunknown='true'
> rs:basecatalog='MSCS_Store_TransactionCo
nfig'
> rs:basetable='ShippingConfig' rs:basecolumn='description'>
> <s:datatype dt:type='string' dt:maxLength='255'/>
> </s:AttributeType>
> <s:AttributeType name='action_page' rs:number='4' rs:nullable='true' rs:writeunknown='true'
> rs:basecatalog='MSCS_Store_TransactionCo
nfig'
> rs:basetable='ShippingConfig' rs:basecolumn='action_page'>
> <s:datatype dt:type='string' dt:maxLength='255'/>
> </s:AttributeType>
> <s:AttributeType name='action_friendly_name' rs:number='5' rs:nullable='true'
> rs:writeunknown='true' rs:basecatalog='MSCS_Store_TransactionCo
nfig'
> rs:basetable='ShippingConfig' rs:basecolumn='action_friendly_name'>
> <s:datatype dt:type='string' dt:maxLength='255'/>
> </s:AttributeType>
> <s:AttributeType name='progid' rs:number='6' rs:nullable='true' rs:writeunknown='true'
> rs:basecatalog='MSCS_Store_TransactionCo
nfig'
> rs:basetable='ShippingConfig' rs:basecolumn='progid'>
> <s:datatype dt:type='string' rs:dbtype='str' dt:maxLength='255'/>
> </s:AttributeType>
> <s:AttributeType name='config' rs:number='7' rs:nullable='true' rs:writeunknown='true'
> rs:basecatalog='MSCS_Store_TransactionCo
nfig'
> rs:basetable='ShippingConfig' rs:basecolumn='config'>
> <s:datatype dt:type='string' rs:dbtype='str' dt:maxLength='2147483647'
> rs:long='true'/>
> </s:AttributeType>
> <s:AttributeType name='enabled' rs:number='8' rs:nullable='true' rs:writeunknown='true'
> rs:basecatalog='MSCS_Store_TransactionCo
nfig'
> rs:basetable='ShippingConfig' rs:basecolumn='enabled'>
> <s:datatype dt:type='int' dt:maxLength='4' rs:precision='10' rs:fixedlength='true'/>
> </s:AttributeType>
> <s:AttributeType name='language_id' rs:number='9' rs:nullable='true' rs:writeunknown='true'
> rs:basecatalog='MSCS_Store_TransactionCo
nfig'
> rs:basetable='ShippingConfig' rs:basecolumn='language_id'>
> <s:datatype dt:type='string' dt:maxLength='128'/>
> </s:AttributeType>
> <s:AttributeType name='shipping_method_type' rs:number='10' rs:nullable='true'
> rs:writeunknown='true' rs:basecatalog='MSCS_Store_TransactionCo
nfig'
> rs:basetable='ShippingConfig' rs:basecolumn='shipping_method_type'>
> <s:datatype dt:type='string' rs:dbtype='str' dt:maxLength='20'/>
> </s:AttributeType>
> <s:AttributeType name='visible' rs:number='11' rs:nullable='true' rs:writeunknown='true'
> rs:basecatalog='MSCS_Store_TransactionCo
nfig'
> rs:basetable='ShippingConfig' rs:basecolumn='visible'>
> <s:datatype dt:type='boolean' dt:maxLength='2' rs:fixedlength='true'/>
> </s:AttributeType>
> <s:AttributeType name='display_rank' rs:number='12' rs:nullable='true'
> rs:writeunknown='true' rs:basecatalog='MSCS_Store_TransactionCo
nfig'
> rs:basetable='ShippingConfig' rs:basecolumn='display_rank'>
> <s:datatype dt:type='int' dt:maxLength='4' rs:precision='10' rs:fixedlength='true'/>
> </s:AttributeType>
> <s:AttributeType name='countries_supported' rs:number='13' rs:nullable='true'
> rs:writeunknown='true' rs:basecatalog='MSCS_Store_TransactionCo
nfig'
> rs:basetable='ShippingConfig' rs:basecolumn='countries_supported'>
> <s:datatype dt:type='string' rs:dbtype='str' dt:maxLength='255'/>
> </s:AttributeType>
> <s:extends type='rs:rowbase'/>
> </s:ElementType>
> </s:Schema>
> <rs:data>
> <z:row shipping_method_id='{00000000-0000-0000-0000-002468008034}' shipping_method_name='Quick'
> description='(7 to 10 business days)'
> action_page='ChargeByQuantity_edit.asp' action_friendly_name='Charge by
> Quantity' progid='commerce.stepwiseshipping'
> config='<DICTIONARY xmlns:dt="uuid:304FB305-29A4-11d3-B0D4-00C04F8ED7A2"
> version="1.0">
> <DICTITEM key="mode"><VALUE dt:dt="i2">1</VALUE></DICTITEM>
> </DICTIONARY>
> ' enabled='1' language_id='en-US' shipping_method_type='Ship' visible='True'
> display_rank='1' countries_supported=''/>
> </rs:data>
> </xml>
>
> Is there a recommended way of packaging a site with table modifications to
> out-of-the-box tables?
>
> Thanks,
> Colin
>
>
>

Colin Bowern

2005-09-26, 6:00 pm

Hi Ravi,

Thanks for tip - it all seems clear now! I just read this in the SDK docs
as well:

The scripts associated with the parameters s_PUPParam2 and s_PUPParam3 exist
in the txt_script column of the pupdbscripts table in the Administration
database. The u_scriptname column contains the name of the script as it appears
in the list specified by this parameter, and the other two columns in that
table, iSiteID and iResourceID, exist to prevent script name clashes between
different resources.

Cheers,
Colin

[vbcol=seagreen]
> Hi Colin,
>
> The way to do this is as follows:
>
> 1. In the MSCS_Admin DB identify the Resource with which the
> shipping_config table is associated (this is the value of the pup1
> fieldname), Resources Table I think.
> 2. The pup2 fieldname value will give you the name of the scriptname
> that
> creates this resource. Look up this field value in the pupdbscripts
> table
> (the long text field contains the scripts for resource creation). If
> you use
> the CommerceConfig PIA model you'll encounter the GetScript/PutScript
> functions. The actual SQL scripts are avilable under the C:\Program
> Files\Microsoft Commerce Server 2002\SDK\Site Create directory. Modify
> the
> ShippingConfig table and use the PutScript to replace the script in
> the
> MSCS_Admin DB for that site.
> 3. Pack the site. This time the default packager will extract the
> correct
> script from the admin db and the data from your site db.
> You would not have problems in unpacking the resource now. Let me know
> if you want more information.
>
> "Colin Bowern" wrote:
>


Colin Bowern

2005-09-26, 6:00 pm

I threw together a command line tool to get/put/delete SQL Scripts from the
pupdbscripts table and posted it at:

http://www.gotdotnet.com/workspaces...a0-b7f284a8c113

Cheers,
Colin
[vbcol=seagreen]
> Hi Ravi,
>
> Thanks for tip - it all seems clear now! I just read this in the SDK
> docs as well:
>
> The scripts associated with the parameters s_PUPParam2 and s_PUPParam3
> exist in the txt_script column of the pupdbscripts table in the
> Administration database. The u_scriptname column contains the name of
> the script as it appears in the list specified by this parameter, and
> the other two columns in that table, iSiteID and iResourceID, exist to
> prevent script name clashes between different resources.
>
> Cheers,
> Colin


Vinayak Tadas[MSFT]

2005-09-27, 2:50 am

Hi Colin,
Thanks for posting this.

Thanks
Vinayak Tadas
Microsoft
http://blogs.msdn.com/vinayakt

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2002 Microsoft Corporation. All rights
reserved.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Get Secure! For more info visit http://www.microsoft.com/security. Please
reply to the newsgroups only


--------------------
| Message-ID: <86cd1bdd1b4f8c790cdae6feed7@msnews.microsoft.com>
| From: Colin Bowern <colin.bowern@nospam.officialcommunity.com>
| Subject: RE: Deploying a Package with Table Modifications
| References: <86cd1bdd1b448c790bb3fae83e8@msnews.microsoft.com>
| MIME-Version: 1.0
| Content-Transfer-Encoding: 8bit
| Content-Type: text/plain; charset=iso-8859-1; format=flowed
| X-Newsreader: JetBrains Omea Reader 671.6
| Newsgroups: microsoft.public.commerceserver.setup.deploymentoperations
| Date: Mon, 26 Sep 2005 13:22:53 -0700
| NNTP-Posting-Host: mail.officialcommunity.net 207.188.77.211
| Lines: 1
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP15.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.commerceserver.setup.deploymentoperations:583
| X-Tomcat-NG: microsoft.public.commerceserver.setup.deploymentoperations
|
| I threw together a command line tool to get/put/delete SQL Scripts from
the
| pupdbscripts table and posted it at:
|
|
http://www.gotdotnet.com/workspaces...3-96dc-41de-9ca
0-b7f284a8c113
|
| Cheers,
| Colin
|
| > Hi Ravi,
| >
| > Thanks for tip - it all seems clear now! I just read this in the SDK
| > docs as well:
| >
| > The scripts associated with the parameters s_PUPParam2 and s_PUPParam3
| > exist in the txt_script column of the pupdbscripts table in the
| > Administration database. The u_scriptname column contains the name of
| > the script as it appears in the list specified by this parameter, and
| > the other two columns in that table, iSiteID and iResourceID, exist to
| > prevent script name clashes between different resources.
| >
| > Cheers,
| > Colin
| >> Hi Colin,
| >>
| >> The way to do this is as follows:
| >>
| >> 1. In the MSCS_Admin DB identify the Resource with which the
| >> shipping_config table is associated (this is the value of the pup1
| >> fieldname), Resources Table I think.
| >> 2. The pup2 fieldname value will give you the name of the scriptname
| >> that
| >> creates this resource. Look up this field value in the pupdbscripts
| >> table
| >> (the long text field contains the scripts for resource creation). If
| >> you use
| >> the CommerceConfig PIA model you'll encounter the GetScript/PutScript
| >> functions. The actual SQL scripts are avilable under the C:\Program
| >> Files\Microsoft Commerce Server 2002\SDK\Site Create directory.
| >> Modify
| >> the
| >> ShippingConfig table and use the PutScript to replace the script in
| >> the
| >> MSCS_Admin DB for that site.
| >> 3. Pack the site. This time the default packager will extract the
| >> correct
| >> script from the admin db and the data from your site db.
| >> You would not have problems in unpacking the resource now. Let me
| >> know
| >> if you want more information.
| >> "Colin Bowern" wrote:
| >>
| >>> I added a few columns to the ShippingConfig table in the
| >>> TransactionConfig database. It seems with these modifications in
| >>> place Site Packager is unable to unpack this resource producing the
| >>> following errors:
| >>>
| >>> [11:59:38] GenericPuP: ImportTableDataFromXMLFile:
| >>> Table=ShippingConfig:
| >>> Load XML Data file for table: ShippingConfig: 0x5E Invalid use of
| >>> Null
| >>> [11:59:38] Error importing object data for Transaction Config from
| >>> file C:\Documents
| >>> and Settings\xxxx\Local Settings\Temp\3\Transaction Config 5:Invalid
| >>> procedure
| >>> call or argument
| >>> The underlying ShippingConfig.xml that is packaged in the site
| >>> reflects all of the proper columns but the database table was not
| >>> created as such:
| >>> <xml xmlns:s='uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882'
| >>> xmlns:dt='uuid:C2F41010-65B3-11d1-A29F-00AA00C14882'
| >>> xmlns:rs='urn:schemas-microsoft-com:rowset'
| >>> xmlns:z='#RowsetSchema'>
| >>> <s:Schema id='RowsetSchema'>
| >>> <s:ElementType name='row' content='eltOnly' rs:updatable='true'>
| >>> <s:AttributeType name='shipping_method_id' rs:number='1'
| >>> rs:writeunknown='true'
| >>> rs:basecatalog='MSCS_Store_TransactionCo
nfig'
| >>> rs:basetable='ShippingConfig' rs:basecolumn='shipping_method_id'
| >>> rs:keycolumn='true'>
| >>> <s:datatype dt:type='uuid' dt:maxLength='16' rs:fixedlength='true'
| >>> rs:maybenull='false'/>
| >>> </s:AttributeType>
| >>> <s:AttributeType name='shipping_method_name' rs:number='2'
| >>> rs:nullable='true'
| >>> rs:writeunknown='true' rs:basecatalog='MSCS_Store_TransactionCo
nfig'
| >>> rs:basetable='ShippingConfig' rs:basecolumn='shipping_method_name'>
| >>> <s:datatype dt:type='string' dt:maxLength='255'/>
| >>> </s:AttributeType>
| >>> <s:AttributeType name='description' rs:number='3' rs:nullable='true'
| >>> rs:writeunknown='true'
| >>> rs:basecatalog='MSCS_Store_TransactionCo
nfig'
| >>> rs:basetable='ShippingConfig' rs:basecolumn='description'>
| >>> <s:datatype dt:type='string' dt:maxLength='255'/>
| >>> </s:AttributeType>
| >>> <s:AttributeType name='action_page' rs:number='4' rs:nullable='true'
| >>> rs:writeunknown='true'
| >>> rs:basecatalog='MSCS_Store_TransactionCo
nfig'
| >>> rs:basetable='ShippingConfig' rs:basecolumn='action_page'>
| >>> <s:datatype dt:type='string' dt:maxLength='255'/>
| >>> </s:AttributeType>
| >>> <s:AttributeType name='action_friendly_name' rs:number='5'
| >>> rs:nullable='true'
| >>> rs:writeunknown='true' rs:basecatalog='MSCS_Store_TransactionCo
nfig'
| >>> rs:basetable='ShippingConfig' rs:basecolumn='action_friendly_name'>
| >>> <s:datatype dt:type='string' dt:maxLength='255'/>
| >>> </s:AttributeType>
| >>> <s:AttributeType name='progid' rs:number='6' rs:nullable='true'
| >>> rs:writeunknown='true'
| >>> rs:basecatalog='MSCS_Store_TransactionCo
nfig'
| >>> rs:basetable='ShippingConfig' rs:basecolumn='progid'>
| >>> <s:datatype dt:type='string' rs:dbtype='str' dt:maxLength='255'/>
| >>> </s:AttributeType>
| >>> <s:AttributeType name='config' rs:number='7' rs:nullable='true'
| >>> rs:writeunknown='true'
| >>> rs:basecatalog='MSCS_Store_TransactionCo
nfig'
| >>> rs:basetable='ShippingConfig' rs:basecolumn='config'>
| >>> <s:datatype dt:type='string' rs:dbtype='str'
| >>> dt:maxLength='2147483647'
| >>> rs:long='true'/>
| >>> </s:AttributeType>
| >>> <s:AttributeType name='enabled' rs:number='8' rs:nullable='true'
| >>> rs:writeunknown='true'
| >>> rs:basecatalog='MSCS_Store_TransactionCo
nfig'
| >>> rs:basetable='ShippingConfig' rs:basecolumn='enabled'>
| >>> <s:datatype dt:type='int' dt:maxLength='4' rs:precision='10'
| >>> rs:fixedlength='true'/>
| >>> </s:AttributeType>
| >>> <s:AttributeType name='language_id' rs:number='9' rs:nullable='true'
| >>> rs:writeunknown='true'
| >>> rs:basecatalog='MSCS_Store_TransactionCo
nfig'
| >>> rs:basetable='ShippingConfig' rs:basecolumn='language_id'>
| >>> <s:datatype dt:type='string' dt:maxLength='128'/>
| >>> </s:AttributeType>
| >>> <s:AttributeType name='shipping_method_type' rs:number='10'
| >>> rs:nullable='true'
| >>> rs:writeunknown='true' rs:basecatalog='MSCS_Store_TransactionCo
nfig'
| >>> rs:basetable='ShippingConfig' rs:basecolumn='shipping_method_type'>
| >>> <s:datatype dt:type='string' rs:dbtype='str' dt:maxLength='20'/>
| >>> </s:AttributeType>
| >>> <s:AttributeType name='visible' rs:number='11' rs:nullable='true'
| >>> rs:writeunknown='true'
| >>> rs:basecatalog='MSCS_Store_TransactionCo
nfig'
| >>> rs:basetable='ShippingConfig' rs:basecolumn='visible'>
| >>> <s:datatype dt:type='boolean' dt:maxLength='2'
| >>> rs:fixedlength='true'/>
| >>> </s:AttributeType>
| >>> <s:AttributeType name='display_rank' rs:number='12'
| >>> rs:nullable='true'
| >>> rs:writeunknown='true' rs:basecatalog='MSCS_Store_TransactionCo
nfig'
| >>> rs:basetable='ShippingConfig' rs:basecolumn='display_rank'>
| >>> <s:datatype dt:type='int' dt:maxLength='4' rs:precision='10'
| >>> rs:fixedlength='true'/>
| >>> </s:AttributeType>
| >>> <s:AttributeType name='countries_supported' rs:number='13'
| >>> rs:nullable='true'
| >>> rs:writeunknown='true' rs:basecatalog='MSCS_Store_TransactionCo
nfig'
| >>> rs:basetable='ShippingConfig' rs:basecolumn='countries_supported'>
| >>> <s:datatype dt:type='string' rs:dbtype='str' dt:maxLength='255'/>
| >>> </s:AttributeType>
| >>> <s:extends type='rs:rowbase'/>
| >>> </s:ElementType>
| >>> </s:Schema>
| >>> <rs:data>
| >>> <z:row shipping_method_id='{00000000-0000-0000-0000-002468008034}'
| >>> shipping_method_name='Quick'
| >>> description='(7 to 10 business days)'
| >>> action_page='ChargeByQuantity_edit.asp' action_friendly_name='Charge
| >>> by
| >>> Quantity' progid='commerce.stepwiseshipping'
| >>> config='<DICTIONARY
| >>> xmlns:dt="uuid:304FB305-29A4-11d3-B0D4-00C04F8ED7A2"
| >>> version="1.0">
| >>> <DICTITEM key="mode"><VALUE dt:dt="i2">1</VALUE></DICTITEM>
| >>> </DICTIONARY>
| >>> ' enabled='1' language_id='en-US' shipping_method_type='Ship'
| >>> visible='True'
| >>> display_rank='1' countries_supported=''/>
| >>> </rs:data>
| >>> </xml>
| >>> Is there a recommended way of packaging a site with table
| >>> modifications to out-of-the-box tables?
| >>> Thanks,
| >>> Colin

|
|

Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com