mORMot Open Source

Thank you very much.  I am using mORMot 1.18 on a new development (following the advice taht mORMot 2 is still not ready for production).

I am somewhat "concerned" - will mORMot 2 be significantly different?  Once started with mORMot 1.18 for a project, what should I do to maintain  the project in the long run?  Will 1.18 be deprecated once mORMot 2 is stable?

Thank you.  It is the mORMot static in memory db (object list).  I checked the manual it seems static in-mem db doesn't support "Not Equal" condition?

I use PostgresSQL. TSQLDBZEOSConnectionProperties

Thank you very much.  The latest patch works!

Hello @ab  Many thanks for the confirmation.   You made my day.  Following your hint, I found the issue.  Thanks again!

This issue won't be detected by Delphi's default MM, and only surfaces up with FastMM in FullDebugMode. And the lesson I learned is: If TSQLRestServerDB holds a reference to TSQLModel, then TSQLModel must be free-ed AFTER TSQLRestServerDB.

destructor TMormotDatabase.Destroy;
begin
  FSQLModel.Free; // <-- this TSQLModel is being free-ed BEFORE TSQLRestServerDB.
  FSQLDBConnectionProps.Free;
  FServer.Free; // <-- FastMM5 in FullDebugMode (and ONLY FullDebugMode) will detect access violation to an already free-ed TSQLModel.

  inherited;
end;

I use Delphi 10.4.2

I'd like to be consistent with mORMot.  So I'll forget about FastMM5, and use mORMot's version of FastMM4, but mORMot's FastMM4 doesn't seem to catch a very simple memory leak?  Does it require FullDebugMode.dll?  What is the correct way to use mORMot's FastMM4 (for better performance and memory safety)?

program Project1;

uses
  FastMM4 in 'FastMM4.pas', // mORMot's version of FastMM4
  Vcl.Forms,
  Unit1 in 'Unit1.pas' {Form1};

{$R *.res}

begin
  ReportMemoryLeaksOnShutDown := True;
  Application.Initialize;
  Application.MainFormOnTaskbar := True;
  Application.CreateForm(TForm1, Form1);
  Application.Run;
end.

procedure TForm1.FormCreate(Sender: TObject);
begin
  var LLeakedObject := TObject.Create;
end;

Here is the small project:

@turkerali

Thank you very much for the heads-up.

I also found the reason why
TSQLRestClientDB.Delete(TMySQLRecord, '') cannot empty the whole table.   The empty SQLWhere cannot be translated to a valid restful DELETE URI.

@ab
So, for best client-server (e.g., postgreSQL server) ORM performance, I should use TSQLRestClientDB.Server to do the Add/Delete/Retrieve/Update?  Or should I use TSQLRestClientDB, for its caching?

Thank you again.

I purchased that book. And I regret big time.

Though it is appreciated that this might be the only published mORMot book on the market, and the table of contents appear very logical and reasonable,  yet the book contents are full of typos, incomplete samples, misleading and incorrect information, and confusing lines out of context!!   The misleading/incorrect information will do you big harm! 

I strongly suggest the author to carefully proofread the book, and fix the typos and correct the wrong information.

Also it claimed to have been proofread by AB - I don't know how he did the "proofread" but the book is of very low publishing quality, I am very upset with the purchase.  This forum and SAD are probably more useful.

This is great to know.

Then how can I perform something like SELECT AVG(Speed) ...WHERE.... GROUP BY xxx? Is it doable with mORMot?