mORMot Open Source

terryc

Member

Registered: 2015-07-04

Posts: 16

How does mORMot handle DDD model upgrade?

Hello,
How does mORMot handle the DDD upgrade? (adding new classes, attributes, associations, or removing same on an existing and in-use model?)

For example, in the basic 01-In Memory ORM demo,
- I compiled the basic demo, ran it a few times, added a few examples and quit, This worked perfectly, data is stored and retrieved. Nice.
- I then added one Number field with the TSynExtended type to the TSQLSampleRecord in the unit SampleData. Compiled. OK.
- I ran the resulting application. And it crashed with an External Sigsegv.

I'm using a form of Agile, and i would expect upwards-compatible modifications to the DDD to be accepted by the ORM. How can i do that?
I do have the capability to track and identify the model changes, if specific actions need to be perform to update the repository.

I'm using Lazarus with FPC 2.7.1.

Thank you for your help.
Best regards,
Thierry

terryc

Member

Registered: 2015-07-04

Posts: 16

Re: How does mORMot handle DDD model upgrade?

Further information: The exception raised is in mormot.pas, class EORMException, TSQLPropInfoRTTI.CreateForm: Unhandled stfFloat/tkFloat type for property Number.

Does mORMot actually handle the extended type?

ab

Administrator

From: France

Registered: 2010-06-21

Posts: 14,272

Website

Re: How does mORMot handle DDD model upgrade?

No, it handles double values only.

This is a SQlite3 restriction, and a cross-platform need.