db: update type of cpu_flags field

Cluster has a column cpu_flags with type text while a host has the same column but with type varchar(4000).
Making these two columns the same solves issues regarding cpu flags longer then 4000 characters.

Signed-off-by: Jasper Berton <[email protected]>

Author: JasperB-TeamBlue

packaging/dbscripts/upgrade/04_05_0310_alter_type_cpu_flags.sql

@@ -0,0 +1 @@
+SELECT fn_db_change_column_type('vds_dynamic','cpu_flags','VARCHAR','TEXT');

packaging/dbscripts/vds_sp.sql

@@ -223,7 +223,7 @@ CREATE OR REPLACE FUNCTION InsertVdsDynamic (
     v_version_name VARCHAR(40),
     v_build_name VARCHAR(40),
     v_previous_status INT,
-    v_cpu_flags VARCHAR(4000),
+    v_cpu_flags TEXT,
     v_pending_vcpus_count INT,
     v_pending_vmem_size INT,
     v_cpu_sockets INT,
@@ -488,7 +488,7 @@ CREATE OR REPLACE FUNCTION UpdateVdsDynamic (
     v_version_name VARCHAR(40),
     v_build_name VARCHAR(40),
     v_previous_status INT,
-    v_cpu_flags VARCHAR(4000),
+    v_cpu_flags TEXT,
     v_pending_vcpus_count INT,
     v_pending_vmem_size INT,
     v_cpu_sockets INT,
@@ -1530,7 +1530,7 @@ LANGUAGE plpgsql;
 
 CREATE OR REPLACE FUNCTION UpdateCpuFlags (
     v_vds_id UUID,
-    v_cpu_flags VARCHAR(4000)
+    v_cpu_flags TEXT
     )
 RETURNS VOID AS $FUNCTION$
 BEGIN