On Apr 9, 2018, at 10:35 PM, Kirk Brooks wrote: > I did not hear anyone talk about SQL. On the other hand I didn't hear > anyone say SQL is dead. My takeaway is it's not a priority - if you're > working in 4D use 4D's data engine. I think SQL is viewed as a connectivity > feature, not a design goal.
I’ll tell you what I heard Laurent say at the lunch table with some other developers when the SQL engine was brought up. He said it is not dead and he wants to improve it. The issue is a 4D Engineering team issue. The guy that wrote the SQL engine is no longer at 4D. They are in the process of adding a team member, actually multiple team members, to maintain and enhance the 4D SQL engine. You don’t just “hire a guy” to do this work. You need quality individuals that are in it for the long term. That’s how you get something good. And If you know anything about Laurent, he is all about doing good, quality work. Would you agree? 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. We are going to wait and see what happens with SQL. They find the right people to work on the project and you will see results. Tim Sent from my iPad ********************************************************************** 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] **********************************************************************
