Geek Culture
Published in

Geek Culture

Identity and Surrogate Keys in FactEngine Query Language (FEQL)

The finer points of how FactEngine semantic parsing works

In the query above, a provider is identified by their name, Kathy Snelling, but how does FactEngine know that a provider is identified by their first name followed by their last name? Why isn’t it last name followed by first name?

If we look at the entity relationship diagram for the schema over which the query operates, we can see that the Provider entity has a primary key of Privider_Id and a…

--

--

--

A new tech publication by Start it up (https://medium.com/swlh).

Recommended from Medium

JavaScript News (December 2017)

Smart Contract Testing with MochaJS

Beginner’s guide to Node.js

Learn React by Building an Expense Tracker App: Child-to-Parent Component Communication (Bottom-up)

Triggering Audio w/ Vanilla JS — Building a Drum Rack!

Building a Push Service that Scales to 1 Million Subscribers with Firebase

Separating web apps — Service Workers

Firestore dynamic querying with multiple conditions(with orderby method)

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Victor Morgante

Victor Morgante

FactEngine. Architect, data scientist, researcher.

More from Medium

Publication Module Decision Points (Schema Details) Mapped for Ten of the S1000D Issues: 1.9 to 5.0

The Sixth Sense | a not so technical guide to sensors

Skills @ Beamery Part 1: Representing skills for today, and the unknown of tomorrow

Okteto as a Sagemaker alternative