> Date: Mon, 09 Apr 2018 23:03:31 -0500 > From: Tim Nevels <timnev...@mac.com> > > The 4D SQL engine is a layer above the 4D database engine. SQL statements > must be translated into a form that the 4D database engine can process. And > that can take many forms. Some would work but be super slow, others could be > optimized to take advantage of the 4D database engine and be fast. So you > have to create a parse that can make this happen. It can be done, but it is > not an easy task. Hence the need for “quality individuals” to make this > happens.
I seem to remember being specifically told back in the early days of v11 that the SQL engine was not a layer on top of the 4D engine, but that it was completely separate. ------------------------------------------------ Richard Wright DataDomain rwri...@datadomainsoftware.com ------------------------------------------------ ********************************************************************** 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:4d_tech-unsubscr...@lists.4d.com **********************************************************************
