mORMot Open Source

Sounds good and fast but the ultimate purpose is to add,edit, delete array's data.
JSONToDataset returns a readonly dataset.
Well i can create from it a clientdataset but .... is there a simply way, when edited,  to synchronize array values to dataset ones? (I,ve not found a DatasetToJSON).

very very tx AB !!!

Hi AB,
I'm beginning to know a bit more your fantastic framework and have a question about ID field : it is defined as Integer.
As stated in doc, in sqlite it is an int64 , but in delphi , AFAIK, it is an int32.
One of my tables will grow till int32 capability in short time (few years I suppose) : is it possible , or planned, to use an int64 for the id property ?

Hi AB,

it isn't a varint issue, but a null field issue.

in mormotsqlite3 , line 644 :

    result^.BindNull(i) else

should be :

    result^.BindNull(i+1) else

Hi tech,
sorry to noise you but, where do you apply the visible property of tSQlMenus to menutabs ?

hi tech ,
thanks for reply.
May you give me an axample of how can you use a dynamic array ?
The constructor method of the ribbon apllies this control on line 1448 :

  assert(TableIndex=Tab.PageIndex); // as expected in SetAction()

that is, if i have correctly undertstood : the tfileribbontabparameter must contain exactly the same tables of the model.

tech an ab thanks a lot.

I have to be more explicit...
The relation among customer and orders is clear : in the order there is a tSQLCustomer...
But what about order and items ?
I think that adding a tSQLOrder in tSQLItem is not a good idea. It is an order property.
Does the framework automatically support this without the need of create a new class TSQLOrdereItems , but simply adding a TSQLItem to TSQLOrder declared as having multiply cadinality ?
Thank you very much

I'm unlike to agreed with WarleyAlex : what a neewby of the frameword needs are elementary samples ,not sources of complex projects.
The master detail explanation in SAD is NOT a master detail sample : how can you say that a one to many relationship is one like this ?
(from SAD) :

TSQLMyFile = class(TSQLRecord) 
private 
    FSecondOne: TSQLMyFileInfo; 
    FFirstOne: TSQLMyFileInfo; 
    FMyFileName: RawUTF8; 
published 
         property MyFileName: RawUTF8 read FMyFileName write FMyFileName; 
         property FirstOne: TSQLMyFileInfo read FFirstOne write FFirstOne; 
         property SecondOne: TSQLMyFileInfo read FSecondOne write FSecondOne; 
end; 

this is a ONE TO TWO relationship : I have perhaps to write also ONE TO THREE ... ONE TO MILLION  classes to satisfy real world cases ?
Your framework has much documentation , but after month of reading and reading it i'm yet not able to do nothing more that not useful project, like your maindemo sample.

Regards

ab,
i've no words !
I cannot understand how you, sleeping as a mormot , can do all what you do.
Weel , clearly thanks, and also the adoption of a little mormot , also if i'm yet far from making a profit from my project!

Mario

Well,

the idea is

Create a new class , inherited from tsqlrecordsigned , with :
a new huge field which will contain all changes , not published;
a startdate  and an enddate published property containing the validity interval (UTC) of properties actually stored in published properties : a row deletion could be marked by and enddate of 0.
The version indicator will be a public property of type tTimeLog with UTC values.
Setting the indicator to a date will permit to store and retrieve values at the desired timestamp (updates will be accepted only for now or  a future date : in this case the changes wil be stored in the log and automatically applied when the date will be reached). Setting the version timelog to 0, will permit to store and retrieve values at current_date.
Define an interface with some common methods, i.e.
  setversiondate(aDate : tTimelog) that will set the version tTimelog to aDate.
  resetversiondate that will set the version property to 0.
  .....
This can be made in a new unit (i hope also fro not published huge field) , but how to define the methods needed to maintain versioning on insert, update, delete and returning values at a desired timestamp on get? Any suggestion will be appreciated.

Yes,  i've read it.
Insertion
no problem old values are all null.
Deletion
I'll add a status field to mark record no more valid : no need to write to log.
Update
I need to know old property values to save them in log structure : are them available at this time ?

Certainly also clients may benefit.
About the patch container it could be, depending on cases, a single table, a specific table for each versioned table or, also , a new variant field ,never exposed to clients : where changes are limited to very few properties and version retrival is frequently asked , this could improve performances.

Thank you very much.
Mario