mORMot Open Source

Maybe Arnaud changes the function DateTimeToSQL() a little bit like this:

function DateTimeToSQL(DT: TDateTime; WithMS: boolean=false; HasTimeChar: Boolean=true): RawUTF8;
const
  TIME_CHAR: array[Boolean] of AnsiChar = (' ', 'T');
...

And replace 'T' with TIME_CHAR[HasTimeChar]

With best regards
Thomas

I have replaced "MoveFast := @MoveX87" by "MoveFast := @System.Move" and the error still remains.

I have tested version 1.18.5999 and there is already the error. The error depends on the constellation shown in the incoming posting.

Bis bald...
Thomas

Hallo!

Thanks for the work. Unfortunately, the problem is not solved. The error occurs both in my program and in the example "30 - MVC Server" (only in RELEASE build).

It's no problem for me. I can continue working with older Delphi versions. If other users report bugs related to Delphi 10.4, you should keep the problem in mind. From my past experience I should have known better, never trust Delphi x.0 versions. But I couldn't resist the new LSP feature.

Thanks again for the time you invest in mORMot.

With best regards
Thomas

Thanks for your help.

When I do a DEBUG build with Delphi 10.4, there is NO error! When I do a RELEASE build, I get the following error message:
000000000000C757  ! EXCOS EAccessViolation (c0000005) [] at 53b770 SynCommons.MoveX87  stack trace API 6f133a mORMot.TInterfaceFactory.Create 6f0504 mORMot.TInterfaceFactory.Get 86cd44 mORMotMVC.TMVCApplication.Start 8867c3 u_VGServerMain.TVGServerMain.Create 886d29 u_VGServerDaemon.TVGServerDaemon.Start
000000000004B051  ! EXCOS EAccessViolation (c0000005) [] at 53b770 SynCommons.MoveX87  stack trace API

Fatal exception EAccessViolation raised with message Zugriffsverletzung bei Adresse 0053B770 in Modul 'VGServer.exe'. Lesen von Adresse 001A4000

The error occurs only when I add the parameter "pmArtikelID: TID" to the function in the example. Otherwise it also works with Delphi 10.4 in RELEASE build.

With Delphi 10.3.3 it works with the DEBUG and the RELEASE build.

If I can do more, please say so.

With best regards
Thomas

Hallo!

Thanks a lot Arnaud for the answer. Yeah, that was in the 1980s. That's when I started learning programming for private purposes.

With best regards
Thomas

Hello,

@mvp, thanks for your answer.
What you are recommending is what I am currently doing as a workaround.
But I think there's a bug after all. Otherwise I can explain the results in
my last example.

@ab, when I look at this test:
- {"TestDouble":"16.2E-2"}  => Wrong: Result 1,62

For me, the input value is parsed to 162 and then converted to a float value.
The decimal separator is simply ignored (is not taken into account). Otherwise
I cannot explain the result. If I test with {"TestDouble":"16,2E-2"} everything
is fine.

I don't know the JSON specification. But I can't imagine that specific country
settings should have an impact on the result. And there should be no difference
if a value is double quoted. Because without double quotes {"TestDouble":16.2E-2},
it works right. Maybe I'm just making a thinking mistake.
I hope I'm not too persistent with my questions.

With best regards

Do you know FreeOffice (http://www.freeoffice.com)?
FreeOffice is free for home and business use. It can create large PDF documents without problems.
SoftMaker has a wonderful Office-Suite. In my experience it is the best alternative to Microsoft Office.

Best regards.