Posted
about 3 years
ago
by
ab
It is necessary on Delphi 2007 - 2010 at least.Buggy compiler.
|
Posted
about 3 years
ago
by
ab
I guess cat /proc/cpuinfo should return something on the VM terminal (not MacOs).The numbers are weird: some are better, other are worse than your previous tests.But very good numbers in all cases.Thanks for the feedback.
|
Posted
about 3 years
ago
by
ab
This is weird, because TDocVariantData.AddValue does not use the late-binding so won't call DispInvoke.Your error message means that DispInvoke() was called with a late-binding method with no name.When occurs exactly the problem (the full call stack
|
Posted
about 3 years
ago
by
ab
You are right.Should be fixed on https://github.com/synopse/mORMot2/commit/4d402b1cIt didn't occur on older Delphi revisions (e.g. XE4/XE7).
|
Posted
about 3 years
ago
by
tbo
Delphi 10.4.2, mORMot2 commit 4d402b1Unit mormot.core.threads.pas, line 2680[dcc32 Hinweis] mormot.core.threads.pas(2680): H2077 Auf 'found' zugewiesener Wert wird niemals benutztTranslation: Value assigned to "found" is never usedWith best regardsThomas
|
Posted
about 3 years
ago
by
Stemon63
OK, perfect.Thanks a lot :-)
|
Posted
about 3 years
ago
by
ab
Yes, the async server seems stable now, with pretty good performance.Our internal tests are very promising. I guess it is stable enough to be run on production.But of course, some issue may occur, as with anything new: please report here if you encounter any problem.
|
Posted
about 3 years
ago
by
tbo
ab wrote:Or just use a TDocVariantData stored into a variant.
+1 I like DocVariants very much. Whenever you get stuck, a DocVariant comes along from somewhere.
|
Posted
about 3 years
ago
by
ab
AOG wrote:The latest mORMot2 (with sqlite3-statics) with the latest FPC trunk (both today) works very well on ARM32 bit.
Thanks Alfred for the feedback! Note that I have backported the FPC trunk fix about TStrRec.RefCnt in mORMot 1 this morning.See https://synopse.info/fossil/info/b701a6f3f93d532a
|
Posted
about 3 years
ago
by
ab
There is no such method directly.Because in practice, it is likely to be slower than always putting all fields.My guess is that a custom method working at ORM level, using TOrmPropInfo.IsValueVoid and TOrmPropInfo.GetVariant could help, if you really need it.
|