Upgrade all database tables that use JSON to be LONGTEXT instead of what they were.

Addresses bug #10825
This commit is contained in:
Colin Kuskie 2009-08-25 21:42:16 +00:00
parent d0dd47a5a4
commit 7fcb339605
5 changed files with 49 additions and 3 deletions

View file

@ -153,31 +153,37 @@ sub definition {
##Collateral data is stored as JSON in here
autoGenerate => 0,
defaultValue => '[]',
fieldType=>"textarea",
},
accessoryJSON => {
##Collateral data is stored as JSON in here
autoGenerate => 0,
defaultValue => '[]',
fieldType=>"textarea",
},
relatedJSON => {
##Collateral data is stored as JSON in here
autoGenerate => 0,
defaultValue => '[]',
fieldType=>"textarea",
},
specificationJSON => {
##Collateral data is stored as JSON in here
autoGenerate => 0,
defaultValue => '[]',
fieldType=>"textarea",
},
featureJSON => {
##Collateral data is stored as JSON in here
autoGenerate => 0,
defaultValue => '[]',
fieldType=>"textarea",
},
benefitJSON => {
##Collateral data is stored as JSON in here
autoGenerate => 0,
defaultValue => '[]',
fieldType=>"textarea",
},
);
push(@{$definition}, {

View file

@ -96,7 +96,7 @@ sub definition {
},
fieldPrice => {
tab => "properties",
fieldType => "text",
fieldType => "textarea",
customDrawMethod => 'drawEditFieldPrice',
label => $i18n->get( 'fieldPrice label' ),
hoverHelp => $i18n->get( 'fieldPrice description'),

View file

@ -163,7 +163,7 @@ sub definition {
defaultValue => '',
},
photo => {
fieldType => 'text',
fieldType => 'textarea',
defaultValue => '[]',
noFormPost => 1,
},