Dmitry Arefiev

@RDPasqua, depends on RAD Studio version. In 10.3 standard JSON library is much faster and reliable.

This issue is fixed in 10.3 Rio. And more is comming in Updates. If to stay with 10.1, then search and install IDE HotFix Pack.

GetValue (@Rec)

https://quality.embarcadero.com/browse/RSP-20857 Will be fixed in 10.3 Update 1

https://quality.embarcadero.com/browse/RSP-20349

No sense, as in the trial to find 100% working guessing

It is impossible to decide for 100%. But possible to guess taking into account ThousandSeparator and DecimalSeparator. It will work in 95.38% of the cases. All other - up to the user.

Oracle 12 extended maximum length of VARCHAR2 to 32Kb. And there always was LONG. CLOB / BLOB are stored in tablespaces. BFILE are stored in external files.

You need to use sslxxxx PostgreSQL connection parameters: https://www.postgresql.org/docs/11/libpq-connect.html#LIBPQ-PARAMKEYWORDS And put them into FireDAC PGAdvanced connection parameter: http://docwiki.embarcadero.com/RADStudio/Tokyo/en/Connect_to_PostgreSQL_(FireDAC)#Connection_Definition_Parameters

Instead of last "Size" reference there should be "Size - 1". Fixed.

@ihx, please, report this issue to https://quality.embarcadero.com

1) This is worth to report, but rather as a feature request. Support for automatic decoding may be done easily using WinHTTP WINHTTP_OPTION_DECOMPRESSION option. And probably already in 10.3 Update 1. As a quick workaround, you can modify System.Net.HttpClient.Win.pas, for example: function TWinHTTPClient.DoExecuteRequest(const ARequest: THTTPRequest; var AResponse: THTTPResponse; const AContentStream: TStream): TWinHTTPClient.TExecutionResult; begin ..... // Enable automatic decoding LOptionValue := WINHTTP_DECOMPRESSION_FLAG_GZIP or WINHTTP_DECOMPRESSION_FLAG_DEFLATE or WINHTTP_DECOMPRESSION_FLAG_ALL; WinHttpSetOption(LRequest.FWRequest, WINHTTP_OPTION_DECOMPRESSION, @LOptionValue, sizeof(LOptionValue)); .... end; 2) THTTPReqResp was using WinINet API directly. In 10.3 it was completely reworked to enable support of other platforms, including Linux, OSX, etc.

Changing method to code below and setting FDPhysFBDriverLink1.Embedded to True will make it working. Without that the only workaround is to renamed fbclient.dll into fbembed.dll. procedure TIBLib.LoadFB(const AVendorHome, AVendorLib: String; AEmbedded, AThreadSafe: Boolean); {$IFNDEF FireDAC_IB_STATIC} const C_FBClient: String = {$IFDEF MSWINDOWS} 'fbclient' {$ENDIF} {$IFDEF POSIX} 'libfbclient' {$ENDIF} + C_FD_DLLExt; C_FBEmbed: String = {$IFDEF MSWINDOWS} 'fbembed' {$ENDIF} {$IFDEF POSIX} 'libfbembed' {$ENDIF} + C_FD_DLLExt; {$ENDIF} begin if AEmbedded then LoadBase(AVendorHome, AVendorLib, AThreadSafe {$IFNDEF FireDAC_IB_STATIC}, [C_FBEmbed, C_FBClient] {$ENDIF}) else LoadBase(AVendorHome, AVendorLib, AThreadSafe {$IFNDEF FireDAC_IB_STATIC}, [C_FBClient, C_FBEmbed] {$ENDIF}); if AEmbedded and (Version >= ivFB030000) then FEmbedded := True; end;

This is something to report to quality.embarcadero.com ...

I am remembering / expecting that "{}" are not supported by SQL Server ODBC driver. Really by ODBC itself (the same with other ODBC drivers). Consider that as limitation of FireDAC SQL Server driver, which uses SQL Server ODBC driver internally.

What is RAD Studio version ?

@Lars Fosdal, this feature is supported for 2008 too. In general, it will produce 3 different syntax's depending on SQL Server version. @Attila Kovacs, no, sorry.

SELECT <your query> OFFSET 19900 ROWS FETCH FIRST 100 ROWS ONLY That for SQL Server 2012 and higher. Different SQL will be generated for older versions.

This is known FireDAC issue: https://quality.embarcadero.com/browse/RSP-20857

Do we have a report for this ?

http://docwiki.embarcadero.com/RADStudio/Tokyo/en/Fetching_Rows_(FireDAC)#Rows_Paging FireDAC transparently modifies SQL command and applies keywords like TOP, OFFSET, etc depending on DBMS. So, why "is not something that FireDAC handles well by itself" ?

This makes language infrastructure more open.

But if at least 1 managed field ...