On Thu, 2011-01-13 at 15:55 +0100, José Mejuto wrote:
> Hello FPC,
>
> Thursday, January 13, 2011, 2:58:30 PM, you wrote:
>
> JvdS> Then that option has to be added. I think it's already possible but you
> JvdS> simply don't know how. (Sql-Server is ODBC only, so that one is fixed.
> JvdS> For fi
Hello FPC,
Thursday, January 13, 2011, 2:58:30 PM, you wrote:
JvdS> Then that option has to be added. I think it's already possible but you
JvdS> simply don't know how. (Sql-Server is ODBC only, so that one is fixed.
JvdS> For firebird there's a 'serverencoding' parameter, or something like
JvdS>
On Thu, 2011-01-13 at 10:32 +0100, José Mejuto wrote:
> Hello FPC,
>
> Thursday, January 13, 2011, 10:03:02 AM, you wrote:
>
> >> ODBC 3.5 was launched around 2000-2001.
> L> But this approach will require changes in packages/odbc/src/odbcsql.inc
> L> like, does not ?:
> L> -pointer(SQLGetDat
Hello FPC,
Thursday, January 13, 2011, 1:01:57 PM, you wrote:
L> Also it seems to me, that when you call ANSI version of ODBC API
L> functions, then you receive data in ANSI encoding.
L> If it is so, then it is always safe use ansitoutf8() (or UTF8Encode())
L> on receved data.
No, because ANSI i
Hello FPC,
Thursday, January 13, 2011, 10:03:02 AM, you wrote:
>> ODBC 3.5 was launched around 2000-2001.
L> But this approach will require changes in packages/odbc/src/odbcsql.inc
L> like, does not ?:
L> -pointer(SQLGetData) :=
L> GetProcedureAddress(ODBCLibraryHandle,'SQLGetData');
L> +
