Ionuț Arțăriși wrote: ... % I wasn't aware of this specific case and since I don't know how many % other columns would be in this same situation I can't advocate % changing to CHAR for all of the VARCHAR2 columns. However I do think % that this specific constraint should only be a CHECK constraint and % the storage format should be irrelevant. % % -Ionuț
Hi Ionuț, chacking your patch I noticed it failed to upgrade postgresql schema. Could you please fix it? % diff --git a/schema/spacewalk/upgrade/spacewalk-schema-1.6-to-spacewalk-schema-1.7/001-rhnServerAction-result_msg-size.sql b/schema/spacewalk/upgrade/spacewalk-schema-1.6-to-spacewalk-schema-1.7/001-rhnServerAction-result_msg-size.sql % new file mode 100644 % index 0000000..7b41ff3 % --- /dev/null % +++ b/schema/spacewalk/upgrade/spacewalk-schema-1.6-to-spacewalk-schema-1.7/001-rhnServerAction-result_msg-size.sql % @@ -0,0 +1,3 @@ % +alter table rhnServerAction modify ( result_msg VARCHAR2(1024 CHAR) ); % + % +commit; % -- % 1.7.6.1 % # alter table rhnServerAction modify ( result_msg VARCHAR2(1024 CHAR) ); ERROR: syntax error at or near "modify" LINE 1: alter table rhnServerAction modify ( result_msg VARCHAR2(102... Regards, -- Michael Mráka Satellite Engineering, Red Hat _______________________________________________ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
