VFP has stirred something
Posted: Fri Mar 08, 2019 3:17 pm
Terry,
I understand what you trying to get over.
Lets take maybe your real life case, you use EF to communicate with an agnostic database, EF has all the knowledge to communicate with any database that implements the EF model, e.g. Npgsql for PostgreSQL.
Now it ends up that we as coders need to write applications that uses the EF framework. No problem.
However, if we can put something in place between our code and EF, lets call it a "knowledge" model, it learns through how/what we want to communicate with the database. Next time we want to do something the Knowledge model "suggest" to us what we want/need, click the yes/no button and it adds that to its knowledge. Short of a long story, the knowledge model interrogate the database and based on changes, next day when we coders arrive at the office the source code of what we planned to do lies ready to test/confirm in our IDE....
Just my "interpretation" and far fetched idea...
I understand what you trying to get over.
Lets take maybe your real life case, you use EF to communicate with an agnostic database, EF has all the knowledge to communicate with any database that implements the EF model, e.g. Npgsql for PostgreSQL.
Now it ends up that we as coders need to write applications that uses the EF framework. No problem.
However, if we can put something in place between our code and EF, lets call it a "knowledge" model, it learns through how/what we want to communicate with the database. Next time we want to do something the Knowledge model "suggest" to us what we want/need, click the yes/no button and it adds that to its knowledge. Short of a long story, the knowledge model interrogate the database and based on changes, next day when we coders arrive at the office the source code of what we planned to do lies ready to test/confirm in our IDE....
Just my "interpretation" and far fetched idea...