mORMot Open Source

Well done!

It might not obvious, but the third parameter called "ForceId" must be "True", in order to save to DB using the ID you assigned.

@mpv, the new SynSM45 is impressive! Thanks for your effort.

Congrats hnb.

I noticed the mORMot-not-included download is no longer available?
You know, some people like me might have already installed mORMOt manually, or prefer to setup mORMot manually, for easy keeping update with the github repos......

Cross-compile feature would be the most needed feature IMHO, because it's the most difficult part for a new Lazarus user, on the other hand, other other tasks, like setting up mORMot for Lazarus, is not that hard.

Currently I'm enjoying Alred's cross-compile distribution

Hello ab,

Actually, there are two kinds of empty files:

  - Log files whose length is 0 byte, and I checked it with a text editor, they are really empty.
  - Log files only has some header info, without any log entry, the following is copied from a real-life log file:

C:\_Data\DelphiDev\app1\App\Bin\app1_Server.exe 0.9.8.932 (2016-07-12 13:59:05)
Host=EDWIN-Notepad User=edwin CPU=4*9-6-15620:FFFBEBBFBFFBFA7D OS=11.1=6.1.7601 Wow64=1 Freq=2143496
Environment variables=
TSynLog 1.18.2774 FTS3 2016-07-12T14:49:47

And my code for setting up the logging:

procedure TServerMgr.SetupServerLogging;
begin
  TSynLog.Family.Level := LOG_VERBOSE;

  TSynLog.Family.AutoFlushTimeOut := 10;
  TSynLog.Family.OnArchive := EventArchiveZip;
  TSynLog.Family.ArchiveAfterDays := 7;
  TSynLog.Family.NoEnvironmentVariable := True;
  TSynLog.Family.LocalTimeStamp := True;

  TSynLog.Family.DestinationPath := GetServerLogsFolder;
  ForceDirectories(TSynLog.Family.DestinationPath);
end;

Any findings

I handle the one-to-many relationships outside of the mORMot, for flexibility, freedom and clarity.

I mean, define the classes like this:

TSQLItem = class(TSQLRecord)
published:
  property HeaderId: TID; // Reference to the master table
end;

TSQLHeader = class(TSQLRecord)
public // not published
  Items: TObjectList<TSQLItem>;
end;

We saving, the program set TSQLItem.HeaderId to the ID of the corresponding header.

When retrieving, the program load the header and item separately, something like:

  myDb.Retrieve(myHeader, aHdrId);
  myHeader.Items := myDb.RetrieveList<TSQLItem>('HeaderID = ?', [], [aHdrId]);

I'm not sure what others think, but to me the built-in support for one-to-many relationship provided by the framework is too limited and not flexible.

And this is why I like mORMot - it finds a very good balance between "an ORM that completely abstract away the relational database concept" and "Directly use TDataSet". In other words, it does the tedious CRUD work excellently for me, while also let me easily take advantages of the proven SQL concept.

Thanks. Will try and test this with Ubuntu sever 16.04 LTS 64bit when I find some time...

@AOG, This is awesome!

Re. the installation path configuration in the future, maybe just add an exe file for changing the path (which is now fixed to "c:\NewPascal")? Actually it's really really really good to just download the .zip files - it's just like the so-called portable programs, which would not force us to do the re-installation after a system re-installation. No installer is needed, that'll cost unnecessary time in maintaining them. We are all developers and we can handle .zip files  

And my testing results:

- win64: There is no win64 compile support, maybe you are missing some files in FPCLazBaseWin32.rar? Result:

Error: Illegal parameter: -Twin64

- win32: Compiled and the tests run successfully.

- linux i386:
    when {$define PUREPASCAL} is on, I got:

      SynCommons.pas(56789,3) Error: Identifier not found "GetCPUID"

    Otherwise I got:

..\fpc-linux32\sqlite3.o:(.data+0xc28): undefined reference to `lstat64'
C:\NewPascal\fpc\units\i386-linux\rtl\si_c21.o: In function `SI_C21_$$__FPC_LIBC21_START':
si_c21.pp:(.text.n_si_c21_$$__fpc_libc21_start+0x27): undefined reference to `__libc_csu_fini'
si_c21.pp:(.text.n_si_c21_$$__fpc_libc21_start+0x2c): undefined reference to `__libc_csu_init'
TestSQL3.dpr(190,1) Error: Error while linking

  - Linux x86_64: Successfully compiled (but did not test running it), with the following added to my .lpr file:

// START http://bugs.freepascal.org/view.php?id=30112
{$ifdef FPC}
  {$ifdef Linux}
    {$ifdef FPC_CROSSCOMPILING}
        {$linklib libc_nonshared.a}
    {$endif FPC_CROSSCOMPILING}
  {$endif Linux}
{$endif FPC}
// END  

Now I want to try AOG's latset Lazarus distribution for cross-compiling for Linux - the Lazarus distribution downloaded from newpascal.org does NOT support cross-compiling for Linux...

@AOG,

Tried, but I absolutely have no idea why it needs the .o file (see logs below) - my compilation target is default (also tried the win32 target).

TestMormotOfficial.lpr(9,1) Error: Can't open object file: fpc-win32\sqlite3.o
TestMormotOfficial.lpr(9,1) Error: Can't open object file: fpc-win32\libkernel32.a
TestMormotOfficial.lpr(9,1) Error: Can't open object file: fpc-win32\libgcc.a

I tried both the TestSQL3.lpi shipped in the official mORMot repository, and also the project file created when started this forum post, like the following:

program TestMormotOfficial;
{$I Synopse.inc}
{$APPTYPE CONSOLE}
uses
  {$I SynDprUses.inc}
  mORMotSelfTests;
begin
  SQLite3ConsoleTests;
end.          

On July 7, 2016 all tests went OK using the newpascal.org distribution: http://synopse.info/forum/viewtopic.php … 989#p20989

@AOG,

I still haven started using Lazarus. So today I downloaded the official mormot and your fork for fpc, I compiled the testsqlit3 project successfully with the fpclazrtticross Lazarus/FPC distribuation you provided earlier.

But interestingly, it emits the following runtime error:

[Window Title]
Error

[Content]
Project TestSQL3 raised exception class 'External: SIGSEGV'.

 At address 458577

[OK]

I think I should download a new version of your cross-compile-ready Lazarus, or download and use the https://github.com/dathox/newpascalpack instead?

I'm a bit confused by the newpascal.org project now - it seems that it integrates your work, but from what I see in the download .zip file, it doesn't contain files for cross-compiling for Linux.

Thanks in advance, for your possible clarification and advises

Great! That did the trick!

I previously tried Release(), but didn't try this one :;

@ab, hey! That's my comment Yes, I'm Edwin Yip

PS, IIRC the fpc/lazarus distribution I downloaded from @AOG's Google Drive does have cross-compile support, isn't the one provided by newpascal.org the same version by @AOG?

Well done BeRo1985! I wish you'll support FPC as well

@BeRo, that would be great!

Would the project backed by a complete test suite for the js langauge? I think that's crucial for quality control

It's defined as

 TBoilerplateHTTPServer = class(TSQLHttpServer)

I see now! Very useful features.

Just one more question - does it work under Linux?

Cool! Just an idea - add some benchmarking

@Maciej,

First, I appreciate and admire your contribution to FPC.

With respect, I would ask, is it really a good idea to change the language name? The bottom line is, the planned FPC fork should provide full backward compatibility for the official FPC.

Re. the website, I would strongly suggest to use github.io. Because you'll be able to collaborate on github.com, because, with respect, I assume github will generally last longer than other webistes But all after all, it'll be the decision you guys should make.

Re. installer, yes, I agree with you, I don't think it's worth to spend the time to make the installer script and compile for each release. We programmers should be able to deal with zip files

@hnb, Wow! Wonderful. And exciting!

@AOG,

Is Mac OS X is o your plan?

Any info about if the AddApplicationToFirewall() function works under Windows 8/8.1/10?

Please be note that "jscript' is not JavaScript nor JS