mORMot

Our ORM is not fully featured, mainly because it is not tied to SQL, but also works with NoSQL like MongoDB or our in-memory engine, so the ORM methods are not 100% aligned to the SQL possibilities.In practice, the limitation to a single field ... [More] location for update comes from the current state of our in-memory engine.So yes, fallback to direct SQL is the way to go for such dedicated cases. [Less]

The SYNOPSE_FRAMEWORK_VERSION constant contains the mORMot version at compile time, on both frameworks.Since yesterday, mORMot 2 also has its build part incremented, e.g. 2.0.10, at each commit.

Ah, Ok.Thanks a lot!Good job!

lagodny wrote:In Ukraine, we now have to fight for our lives and the lives of our families. I ask everyone to bring the truth to the Russians. Because their lies have already crossed all boundaries. Stop the war! If only all Russians were properly ... [More] informed it would probably have ended this war by now. Many of them simply had no idea what was happening. Luckily ugly propaganda cannot hide the consequences of the sanctions, which will be a wake up call for many. The turning point is when the propaganda is  no longer effective and people realize that their country is the brutal aggressor. The only way putin can stay in power somewhat longer is through martial law. In this case it's main purpose is to mislead and silence the inside opposition. [Less]

Mormot1 does not support cross-platform JSON serialization / unserialization for records. Am I wrong?Will that change in mormot2?The main reason of asking is the use of RecordLoadJson/DynArrayLoadJson in getters/setters in TOrm derived entitles.

First ensure you have the latest version of mORMot and SQlite3 static bindings.Then I don't see why custom indexes would induce such an error.Try to circumvent the problem.

In Ukraine, we now have to fight for our lives and the lives of our families. I ask everyone to bring the truth to the Russians. Because their lies have already crossed all boundaries. Stop the war!

There are several ways to do it in TRestStorageExternal.The TRestStorageExternal.OnEngineAddComputeID method is defined for computing an ID before the INSERT.You can put here some low-level SQL statement to get an ID, e.g. from a DB sequence.If you ... [More] want to let the DB create the ID, you may just set TRestStorageExternal.EngineAddForcedID to a non 0 value. But note that this "fake" value will be returned by the ORM, not the actual ID value as inserted by the DB. [Less]

Thank you very much. I'll check this out and see if I can get my head around it. I really appreciate the point in the right direction!Out of curiosity - just wondering why the demo is labelled JSON when there's no JSON packet involved, or is it also JSON and there's something I'm misunderstanding?

Great! Downloading Thanks for your great job, as aways!