James, I am really glad you replied. Your story just goes to show that we all can learn a thing or two, even with decades of experience.
To help you out, SQL (sometimes called sequel) is short for structured query language and it's the preferred `lingua de franca` for so many relational database engines today. A relational database engine allows programmers to store information into things called `tables`, and then programmers can write SQL to query back interesting results from that data. SQL can also be used to insert update and delete, and by putting everything together we can write a CRUD (created read update deleted) application. To make using relational database engines even easier for programming many people have turned to using an ORM in place of SQL. An ORM is short for Object Relational Mapping and usually takes the form of a class library framework such as Hibernate or Entity Framework. These ORM frameworks allow you to write plain old objects, but map them to database tables, thus simplifying the data access layer by removing your requirements to learn SQL, at least that's the idea. In reality, all the ORMs actually just translate the programming code of your language of choice into SQL, which is where the need for a program like I present as an example program arises. That need is to monitor the SQL as it's being generated by the ORM to ensure your code is being translated into SQL efficiently. As any single ORM framework can talk to a variety of relational database engines, this example bridges the gap by allowing one universal tool to monitor them all. There are so many more fun things to learn about SQL and ORM, and they are very relevant today. Even a 45 year prgoramming verteran can learn new things!
_______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
