OS Query Class versus PG Views
andyh at totallybrilliant.com
Sun Aug 21 19:33:11 UTC 2022
Thats a fair point - but something I have got used to :)
Totally Brilliant Software Inc
Phone (US) : (863) 409 4870
Phone (UK) : 0207 193 8582
Web : www.totallybrilliant.com
Helpdesk : http://totallybrilliant.kayako.com
Email : andyh at totallybrilliant.com
On Aug 21, 2022, 3:29 PM -0400, Doug Easterbrook via omnisdev-en <omnisdev-en at lists.omnis-dev.com>, wrote:
> I would use omnis queries and table classes.
> In our app, we’ve for it set up so you can join as many tables as you want in a query and pick the fields you want.
> and, being a little bit creative, we wrote our table classes so that you can update against queries (onl the main table, and not the joins)_. thats some thing you can’t do in sql. but its really convenient
> why we avoid Postgres views: they are just something else to maintain. I’ve had issues altering fields in tables in the past when there are views that are dependant on it. you ave to drop the views and recreate them, so there is database maintenance — which is something you have to write into your upgrade routines because of the dependancy.
> Doug Easterbrook
> Arts Management Systems Ltd.
> mailto:doug at artsman.com
> Phone (403) 650-1978
> > On Aug 21, 2022, at 7:16 AM, Martin Obongita via omnisdev-en <omnisdev-en at lists.omnis-dev.com> wrote:
> > Hello to All,
> > From your experiences, which is a more efficient way working with SQL queries, from within Omnis query classes or creating views in a postgres database?
> > Rgds,Martin.
> > _____________________________________________________________
> > Manage your list subscriptions at https://lists.omnis-dev.com
> > Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com
> Manage your list subscriptions at https://lists.omnis-dev.com
> Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com
More information about the omnisdev-en