I’ll be interested in learning how this differs from Views, not necessarily 4D’s rather simplistic implementation, but something like Oracle’s, along with their very powerful SQL implementation.
------------------------------------------------ Richard Wright DataDomain [email protected] ------------------------------------------------ > Date: Mon, 09 Apr 2018 12:32:09 -0500 > From: Tim Nevels <[email protected]> > > Something that may not be immediately obvious is that using ORDA will reduce > the amount of code needed to query the database. In relational databases you > have to query this table, join to another table, query selection, relate > many, etc. We are all used to doing this and we need to know exactly what the > database structure is. What table is the one table, what table is the many > table, is there a many-to-many intermediate table we need to deal with, etc. > > ORDA can remove the need to know this level of detail in many cases. By > naming relations in a “logical” way you can write code to get the “manager” > of an employee, or get the “direct reports" for an employee. And from that > you can then further filter the results by using a “query” member function. > You let the 4D database figure out if it needs to relate many selection, or > relate one selection for you. And you can make these named relations very > complex if you want. There is a lot of power here that is just starting to be > exposed. ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
