An app needs a “Setup the Database” routine correct ?
Yep, like others, we do that, the installer creates a database and a
But then the Omnis code creates tables and columns from its own Schema
Any changes down the line in the schemas are also handled by the code,
Be careful of schema versions, if someone logs in with an old lib, you
don’t want the code to revert to an old schema definition, potentially
losing columns (fields) of data.
We store the database structure version within the database, so it knows
if it can be updated.
Joins, if your using tables for queries then check out the $fromclause…
this is a good place for joins leaving the where clause to do its job…
Based in Chester in the UK.
On 24/01/2018 20:29, Das Goravani wrote:
> 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.
> And I need a heads up on maybe they’re called “joins”… that which makes it possible to easily pull in associated parent or child records (I don’t know which way it goes). I’ve heard it hinted that this is possible so that it’s less work and quicker. I don’t know what words to look up.
> I heard the word “nextval()” from Bastiaan so today I’m studying “create sequence” and “nextval” for that functionality.
> I just need to hear the words so I can look it up. Of course more than the words is good too. 🙂 Pointers, help, welcome.
> Manage your list subscriptions at lists.omnis-dev.com
Manage your list subscriptions at lists.omnis-dev.com