An app needs a "Setup the Database" routine correct ?

Sten-Erik Björling s-e.bjorling at
Wed Jan 24 15:42:26 EST 2018


If you are using the object-centric approach for programming the interactions with the databases then the construct can contain the routine to create the individual table by SQL if the corresponding table for the object do not exist.

Take care, all the best…



> 24 jan. 2018 kl. 21:29 skrev Das Goravani <das at>:
> When you have say a vertical app moreso than a single enterprise using an app you constantly maintain as more of an IT person, you need a routine in the Vertical which is the “Setup the Database” routine, and would make server tables from schema’s say, make the indexes, create sequencing tables, would basically prepare the database for use.  This routine would be first in the “utilities” section of the app. 
> Does this sound correct?  A setup the database routine that’s all worked out so you don’t have to do anything manually to setup the database?
> Just wanted to check before I write one.  

Sten-Erik Björling
Enviro Data
Kyrkogatan 5A 2 tr
SE-972 32  Luleå

E-Mail: s-e.bjorling at
Mobile: +46-70-655 11 72
Wire: @stenerikbjorling
Skype: stenerikbjorling
iChat: stene at
FaceTime: stene at
Hotmail / Messenger: stenerikbjorling at
GMail: stenerikbjorling at


This email and any files transmitted with it are confidential, may be legally privileged and are intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient, please note that any use, distribution, or reproduction of the contents of this email is strictly prohibited and may be unlawful. If you are not the intended recipient, please notify the sender by return email and destroy all copies of the original message including any attachments thereto. Thank you.

Please note that we take reasonable precautions to prevent the transmission of viruses; however, we cannot guarantee that this email or its attachments are free from viruses. We only send and receive emails on the basis that we are not be liable for any loss or damage resulting from the opening of this message and/or attachments.

More information about the omnisdev-en mailing list