Dmitry Arefiev

BTW, the test suite in above link is 98% successfully passed by 10.3.1 System.JSON. From 7 failing tests, 3-4 may be considered as a "feature" ...

We have two problems: 1) REST, DBX, System.JSON duplicating JSON serialization classes. 2) Non complete docu for (1) classes. We want to keep only System.JSON with options for backward compatibility with REST, DBX. And only to develop System.JSON. When this will happen, then all demos, tests (internal), docu, must be updated to reflect the current RTL state. Now it is not the time for docu work ...

function JsonEncodeString(const AStr: string): string; var LStr: TJSONString; begin LStr := TJSONString.Create(AStr); try Result := LStr.ToJSON; Result := Result.Substring(1, Result.Length - 2); finally LStr.Free; end; end; It expects AStr without double quotes, and returns text without double quotes. You can adjust it to your own needs. There are several options, eg with/without double quotes, encode non-ASCII chars/do not encode, etc. Probably more simple to implement the above according your needs.

In short future this and other IDE performance issues will be resolved ... I hope 🙂

1. You can see this info in hint for component. 2. Because it serves not only as "Component Palette". 3. Not sure, for example me, need it ...

The upcoming 10.3.2 Update will address all above issues. They are really reported in JIRA. Stay tuned ...

May be a bit unexpected approach. And sorry not C but JS, but they are close here. uses System.JSON; function StripJSSlashes(const AStr: string): string; var LVal: TJSONValue; begin LVal := TJSONObject.ParseJSONValue('"' + AStr + '"', False, True); try Result := TJSONString(LVal).Value; finally LVal.Free; end; end;

Great. Thank you for testing.

Once the exception has been raised, it's considered having notified the caller.

https://www.syntevo.com/smartgit/

Using Array DML, or as I wrote above - TFDBatchMove, you can get even better speed.

TFDTable produces many additional queries to mimic TTable and to maintain Live Data Window: http://docwiki.embarcadero.com/RADStudio/Tokyo/en/Browsing_Tables_(FireDAC)#Live_Data_Window_Mode

1) If you need the speed, then dont use TFDTable. At least, use TFDQuery. 2) Consider to use TFDBatchMove with SQLReader from XLS / ODBC data source. And SQLWriter to SQLite DB.

@A.M. Hoornweg, I created and attached experimental patch. Please, try it and let me know. If all is OK, then I will include it into next 10.3 update. grid.patch

http://docwiki.embarcadero.com/RADStudio/Tokyo/en/Using_SQLite_with_FireDAC#Adjusting_FireDAC_Mapping Read sentence "For an expression in a SELECT list ..."

Is it bad to use official DLL ? Several questions: * are you limited in distributing capabilities of this DLL (license, space, what ever) ? * who will support you, when something is broken, and you are using non-official connectivity ? * with whom you you can discuss your connectivity problems on INet, if you are using some from 3d party ? * how long will live your software, when 3d party provider is out of business, and DLL "insides"/protocol are changed ?

This is IProviderSupport or IProviderSupportNG.

Yes, it is.

This issue was (most probably) fixed in 10.2.2. Your workaround is almost correct.

You can do, when both conditions are met: * TOracleDataSet and TgQuery both are inherited from TDataSet * and properly implement IProviderSupport methods: procedure Form1.Proc1( aQry : TDataSet ); begin ... aQry.Close; (aQry as IProviderSupport).PSSetCommandText('select * from xyz'); aQry.Open; ... end;

Could you please provide some tickets to better understand what and where.

https://www.wireshark.org/ https://www.telerik.com/fiddler

In this case I would try to capture HTTP packets sent from 10.1.2 and 10.2.1 clients. And will try to understand what is the difference between them, which may lead to this failure ...

This is not related to REST client. But is related to REST server, which is accessing to InterBase server. And due to some reason the database specified in FireDAC connection parameters is not available. Start from checking your InterBase interbase.log ...

The patch and instruction is published there: https://quality.embarcadero.com/browse/RSP-23656