You are not logged in.
Pages: 1
Hi Arnaud, First of all thank you very much for all the work you've done with mORMot and the great interest that you take to answer our questions.
I began in computing a lot of years ago, when we stored files in diskettes, and so the space was very important.
As you say we are in the 21st century and we have to start thinking differently.
So I must change my mind, because I want adopt a "mORMot"
Regards,
Josep
Hi,
I'm testing Mormot with SQL Server 2008 and when I define TSQLRecord with an Integer or Boolean fields those are translated to SQL Server 2008 as bigint. Sample:
type
TPerson = class(TSQLRecord)
private
fName: RawUTF8;
fAge: Integer;
fHasFacebook: Boolean;
published
property Name: RawUTF8 index 80 read fName write fName;
property Age: Integer read fAge write fAge;
property HasFacebook: Boolean read fHasFacebook write fHasFacebook;
end;
Are translated to SQL Server as:
CREATE TABLE [dbo].[Person](
[ID] [int] NOT NULL,
[Name] [nvarchar](80) NULL,
[Age] [bigint] NULL,
[HasFacebook] [bigint] NULL,
PRIMARY KEY CLUSTERED
...
To save space in the Database, it is possible to configure Mormot to change this behavior?
For example I would like that a Delphi Boolean field becomes a bit field in SQL Server
or and Delphi Integer field becomes also a Integer (4 bytes) in SQL Server?
Regards,
Josep
You are right, is hard to find information about "Firedac Reflection".
Thanks for your time i will investigate interface-based services
It is psossibe use FireDac Refection with mORMot Interface Services?
I Know that Fireddac reflection is not the best solution but for me is easy way to send client updated delta datasets to the server and then Apply Updates
Also FireDact datasets are compatible with livbindings.
Thank's
Pages: 1