mORMot Open Source

DidiL

Member

Registered: 2015-01-06

Posts: 10

Investigating about productivity

Hi ab,

I'm about to start a new n-Tiers project, and I need to make a definitive choice this week about the framework/tools.
My background:
Delphi, ICS/Midware, RemObjects/custom ORM, RO/DA, Intraweb, .
HTML, a few CSS, and basic understanding of Javascript.

My project is a management application in a LAN.
One desktop rich client with word processing, file up/download, reporting...
3 web clients (pc and tablets) for display and some data input.
About 40 tables, up to 3-4 master/detail levels.

I've been reading a lot and testing a few about DDD and SOLID design for a few weeks.
I really see the mid/long term value in this new way out of RAD.
For the moment I plan to go: SQLite, ORM, Delphi client + SmartMS
BUT, I need to make sure I'll be able to be productive, or at least save equivalent time compared to debugging RAD!

- I'm going to investigate mORMotUI wich seem really flexible:
- is there a dedicated demo?
- Some support for simple record data input?
Another aspect:
- What is the recommended way to manage changes in object definition (ie. renaming or changing a field type)?

Thank for your inputs!

ab

Administrator

From: France

Registered: 2010-06-21

Posts: 14,206

Website

Re: Investigating about productivity

There is no dedicated demo about mORMotUI.
It is used in the SynDBExplorer tool, and some of our former projects - but I can't release their source..
There are several items in the roadmap about enhancing mORMotUI.

Any new property in the TSQLRecord class will be added at SQL level, with a ALTER TABLE ADD COLUMN.

But renaming should be done manually, as changing a field type.
SQLite3 does only support ALTER TABLE ADD COLUMN syntax - see https://www.sqlite.org/lang_altertable.html
For identifying the database revision, there is a user_version parameter to TSQLRestServerDB.CreateMissingTables().
This TSQLRestServerDB.CreateMissingTables method is where the table layout is checked and updated if necessary.

The proper way to do it is to create a new record