Question: Who is the programming language that has the WHERE clause partially named after?

full_context: Document 1: Database: The relational model, first proposed in 1970 by Edgar F. Codd, departed from this tradition by insisting that applications should search for data by content, rather than by following links. The relational model employs sets of ledger-style tables, each used for a different type of entity. Only in the mid-1980s did computing hardware become powerful enough to allow the wide deployment of relational systems (DBMSs plus applications). By the early 1990s, however, relational systems dominated in all large-scale data processing applications, and as of 2015[update] they remain dominant : IBM DB2, Oracle, MySQL and Microsoft SQL Server are the top DBMS. The dominant database language, standardised SQL for the relational model, has influenced database languages for other data models.[citation needed]
Document 2: Donald Haderle: Donald Haderle is an American computer scientist and IBM Fellow, best known for his work on relational database management systems (RDBMS). He led the architecture and design of DB2, one of the first commercial RDBMSs, which led to his moniker "Father of DB2." DB2 debuted on IBM's mainframe system MVS in 1983 and validated the applicability of relational databases for high performance transaction processing. With DB2 enterprises store, retrieve, and analyze their business transaction data. The cited reference describes the early technology hurdles, the shift from a monolithic architecture to a distributed architecture portable across many operating systems (Unix, Windows, OS/2, and others) and the technology collaborations with IBM Research. DB2 is used in most enterprises around the world.
Document 3: Delete (SQL): In the database structured query language (SQL), the DELETE statement removes one or more records from a table. A subset may be defined for deletion using a condition, otherwise all records are removed. Some DBMSs, like MySQL, allow deletion of rows from multiple tables with one DELETE statement (this is sometimes called multi-table DELETE).
Document 4: Truncate (SQL): In SQL, the codice_1 statement is a Data Definition Language (DDL) operation that marks the extents of a table for deallocation (empty for reuse). The result of this operation quickly removes all data from a table, typically bypassing a number of integrity enforcing mechanisms. It was officially introduced in the standard.
Document 5: Database: Just as the navigational approach would require programs to loop in order to collect records, the relational approach would require loops to collect information about any one record. Codd's solution to the necessary looping was a set-oriented language, a suggestion that would later spawn the ubiquitous SQL. Using a branch of mathematics known as tuple calculus, he demonstrated that such a system could support all the operations of normal databases (inserting, updating etc.) as well as providing a simple system for finding and returning sets of data in a single operation.
Document 6: Database: IBM also had their own DBMS in 1966, known as Information Management System (IMS). IMS was a development of software written for the Apollo program on the System/360. IMS was generally similar in concept to CODASYL, but used a strict hierarchy for its model of data navigation instead of CODASYL's network model. Both concepts later became known as navigational databases due to the way data was accessed, and Bachman's 1973 Turing Award presentation was The Programmer as Navigator. IMS is classified[by whom?] as a hierarchical database. IDMS and Cincom Systems' TOTAL database are classified as network databases. IMS remains in use as of 2014[update].
Document 7: Database: IBM started working on a prototype system loosely based on Codd's concepts as System R in the early 1970s. The first version was ready in 1974/5, and work then started on multi-table systems in which the data could be split so that all of the data for a record (some of which is optional) did not have to be stored in a single large "chunk". Subsequent multi-user versions were tested by customers in 1978 and 1979, by which time a standardized query language – SQL[citation needed] – had been added. Codd's ideas were establishing themselves as both workable and superior to CODASYL, pushing IBM to develop a true production version of System R, known as SQL/DS, and, later, Database 2 (DB2).
Document 8: Order by: An codice_1 clause in SQL specifies that a SQL codice_2 statement returns a result set with the rows being sorted by the values of one or more columns. The sort criteria do not have to be included in the result set. The sort criteria can be expressions, including column names, user-defined functions, arithmetic operations, or codice_3 expressions. The expressions are evaluated and the results are used for the sorting, i.e., the values stored in the column or the results of the function call.
Document 9: MySQL: MySQL ( "My S-Q-L") is an open-source relational database management system (RDBMS).  Its name is a combination of "My", the name of co-founder Michael Widenius's daughter, and "SQL", the abbreviation for Structured Query Language.
Document 10: Update (SQL): An SQL UPDATE statement changes the data of one or more records in a table. Either all the rows can be updated, or a subset may be chosen using a condition.
Document 11: InnoDB: InnoDB became a product of Oracle Corporation after its acquisition of Finland-based Innobase Oy in October 2005. The software is dual licensed; it is distributed under the GNU General Public License, but can also be licensed to parties wishing to combine InnoDB in proprietary software.
Document 12: Having (SQL): A codice_1 clause in SQL specifies that an SQL codice_2 statement should only return rows where aggregate values meet the specified conditions. It was added to the SQL language because the codice_3 keyword could not be used with aggregate functions.
Document 13: Alias (SQL): An alias is a feature of SQL that is supported by most, if not all, relational database management systems (RDBMSs). Aliases provide database administrators, as well as other database users, with the ability to reduce the amount of code required for a query, and to make queries simpler to understand. In addition, aliasing can be used as an obfuscation technique to protect the real names of database fields.
Document 14: Where (SQL): A codice_1 clause in SQL specifies that a SQL Data Manipulation Language (DML) statement should only affect rows that meet specified criteria. The criteria are expressed in the form of predicates. codice_1 clauses are not mandatory clauses of SQL DML statements, but can be used to limit the number of rows affected by a SQL DML statement or returned by a query. In brief SQL WHERE clause is used to extract only those results from a SQL statement, such as: SELECT, INSERT, UPDATE, or DELETE statement.
Document 15: Brian Aker: Brian Aker, born August 4, 1972 in Lexington, Kentucky, US is an open-source hacker who has worked on various Apache modules, the Slash system, and numerous storage engines for the MySQL database. Aker was Director of Architecture at MySQL AB until it was acquired by Sun Microsystems. He led Sun's web scaling research group, where he worked on the Drizzle database project. He later became a Distinguished Engineer for Sun Microsystems. He left Sun Microsystems after Oracle acquired it. After leaving Sun Microsystems he became the CTO of Data Differential and provided support to open source projects such as libmemcached, Gearman and the Drizzle database project. Aker is currently a Fellow and VP at Hewlett Packard Enterprise.
ground_truth: Michael Widenius's daughter
sub_queries: WHERE >> part of Answer: SQL
SQL has the name of who? Answer: Michael Widenius's daughter