File 1234-Allow-larger-column-sizes-than-8001-in-cas... of Package erlang

Overview Repositories Revisions Requests Users Attributes Meta

File 1234-Allow-larger-column-sizes-than-8001-in-case-DB-suppo.patch of Package erlang (Revision bf6cd7f92ad3019d8dc2ad8158b2b053)

Currently displaying revision bf6cd7f92ad3019d8dc2ad8158b2b053 , Show latest

From 53ef5df40c733ce3d8215c5c98805f99f378f656 Mon Sep 17 00:00:00 2001
From: Igor Raits <igor@gooddata.com>
Date: Thu, 9 Mar 2023 10:17:22 +0100
Subject: [PATCH] Allow larger column sizes than 8001 in case DB supports it

In PostgreSQL, the TEXT field can easily have more than 8001 characters
and it does return the actual number. The size == 0 would happen in case
of some DBs won't return valid value where we would keep the same
behavior as of now.

Signed-off-by: Igor Raits <igor@gooddata.com>
---
 lib/odbc/c_src/odbcserver.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/odbc/c_src/odbcserver.c b/lib/odbc/c_src/odbcserver.c
index 5a01630cbc..604f723803 100644
--- a/lib/odbc/c_src/odbcserver.c
+++ b/lib/odbc/c_src/odbcserver.c
@@ -1328,7 +1328,7 @@ static db_result_msg encode_column_name_list(SQLSMALLINT num_of_columns,
 				       &nullable)))
 	    DO_EXIT(EXIT_DESC);
 
-	if(sql_type == SQL_LONGVARCHAR || sql_type == SQL_LONGVARBINARY || sql_type == SQL_WLONGVARCHAR)
+	if(size == 0 && (sql_type == SQL_LONGVARCHAR || sql_type == SQL_LONGVARBINARY || sql_type == SQL_WLONGVARCHAR))
 	    size = MAXCOLSIZE;
     
 	(columns(state)[i]).type.decimal_digits = dec_digits;
-- 
2.35.3

Places

File 1234-Allow-larger-column-sizes-than-8001-in-case-DB-suppo.patch of Package erlang (Revision bf6cd7f92ad3019d8dc2ad8158b2b053)

Places