Talk:Database Lookup (Lookup Specification) - Revision history

Dgreenwood: /* Devon 10/22/2025 */

2025-10-30T13:45:42Z

Devon 10/22/2025

← Older revision		Revision as of 08:45, 30 October 2025
Line 15:		Line 15:
	=== Devon 10/22/2025 ===		=== Devon 10/22/2025 ===
	* In the SQL Queries Supademos, the bot reads SQL Query as "S-Q-L Query" and AS Clause as "A-S Clause." It's minor, but I think it would be a good idea to edit the voiceover so the bot reads the terms as how humans would say it. It's jarring to the ear otherwise.		* In the SQL Queries Supademos, the bot reads SQL Query as "S-Q-L Query" and AS Clause as "A-S Clause." It's minor, but I think it would be a good idea to edit the voiceover so the bot reads the terms as how humans would say it. It's jarring to the ear otherwise.
	** Dylan 10/30/2025 It's probably ok if the bot reads S-Q-L instead of "~~see~~ quill" or "seek wool" or whatever phonetic pronunciation you want to attempt. S-Q-L is an accepted pronunciation. But this is a good catch for the AS clause. You should get the bot to read that as "as".		** Dylan 10/30/2025 It's probably ok if the bot reads S-Q-L instead of "sea quill" or "seek wool" or whatever phonetic pronunciation you want to attempt. S-Q-L is an accepted pronunciation. But this is a good catch for the AS clause. You should get the bot to read that as "as".

Dgreenwood: /* Devon 10/22/2025 */

2025-10-30T13:45:12Z

Devon 10/22/2025

← Older revision		Revision as of 08:45, 30 October 2025
Line 15:		Line 15:
	=== Devon 10/22/2025 ===		=== Devon 10/22/2025 ===
	* In the SQL Queries Supademos, the bot reads SQL Query as "S-Q-L Query" and AS Clause as "A-S Clause." It's minor, but I think it would be a good idea to edit the voiceover so the bot reads the terms as how humans would say it. It's jarring to the ear otherwise.		* In the SQL Queries Supademos, the bot reads SQL Query as "S-Q-L Query" and AS Clause as "A-S Clause." It's minor, but I think it would be a good idea to edit the voiceover so the bot reads the terms as how humans would say it. It's jarring to the ear otherwise.
			** Dylan 10/30/2025 It's probably ok if the bot reads S-Q-L instead of "see quill" or "seek wool" or whatever phonetic pronunciation you want to attempt. S-Q-L is an accepted pronunciation. But this is a good catch for the AS clause. You should get the bot to read that as "as".

Randallkinard: /* Reanna Patton 10/22/2025 */

2025-10-29T14:29:19Z

Reanna Patton 10/22/2025

← Older revision		Revision as of 09:29, 29 October 2025
Line 3:		Line 3:
	** I now see it's located at the bottom of the page. I would note somewhere that the information will be at the bottom of the page or maybe link to the section in the article.		** I now see it's located at the bottom of the page. I would note somewhere that the information will be at the bottom of the page or maybe link to the section in the article.
	* Under "Test a Database Lookup" what is "appropriate data"?		* Under "Test a Database Lookup" what is "appropriate data"?
	** '''addressed'''		** '''Randall Kinard 10/28/2025 - addressed'''
	* Under "Step by Step Query Edit" #6 says "you" when it should be "your".		* Under "Step by Step Query Edit" #6 says "you" when it should be "your".
	** '''addressed'''		** '''Randall Kinard 10/28/2025 - addressed'''
	* Step by Step Query Edit supademo: "Add a space after the "SELECT" claue" should be clause. The error is also in the AI voiceover.		* Step by Step Query Edit supademo: "Add a space after the "SELECT" claue" should be clause. The error is also in the AI voiceover.
	** '''addressed'''		** '''Randall Kinard 10/28/2025 - addressed'''
	* Step by Step Query Edit supademo: Two of the slides have the AI voice over saying "Press Pace" instead of "Press Space".		* Step by Step Query Edit supademo: Two of the slides have the AI voice over saying "Press Pace" instead of "Press Space".
	** '''addressed'''		** '''Randall Kinard 10/28/2025 - addressed'''
	* "How Fields are Populated" second to last bullet point "Data types" should be "Data Types".		* "How Fields are Populated" second to last bullet point "Data types" should be "Data Types".
	** '''addressed'''		** '''Randall Kinard 10/28/2025 - addressed'''

	=== Devon 10/22/2025 ===		=== Devon 10/22/2025 ===
	* In the SQL Queries Supademos, the bot reads SQL Query as "S-Q-L Query" and AS Clause as "A-S Clause." It's minor, but I think it would be a good idea to edit the voiceover so the bot reads the terms as how humans would say it. It's jarring to the ear otherwise.		* In the SQL Queries Supademos, the bot reads SQL Query as "S-Q-L Query" and AS Clause as "A-S Clause." It's minor, but I think it would be a good idea to edit the voiceover so the bot reads the terms as how humans would say it. It's jarring to the ear otherwise.

Randallkinard: /* Reanna Patton 10/22/2025 */

2025-10-29T14:26:34Z

Reanna Patton 10/22/2025

← Older revision		Revision as of 09:26, 29 October 2025
Line 2:		Line 2:
	* Where can people go to understand what the Lookup Options do and how to apply it to their use case?		* Where can people go to understand what the Lookup Options do and how to apply it to their use case?
	** I now see it's located at the bottom of the page. I would note somewhere that the information will be at the bottom of the page or maybe link to the section in the article.		** I now see it's located at the bottom of the page. I would note somewhere that the information will be at the bottom of the page or maybe link to the section in the article.
	* Under "Test a Database Lookup" what is "appropriate data"?		* Under "Test a Database Lookup" what is "appropriate data"?
	* Under "Step by Step Query Edit" #6 says "you" when it should be "your".		** '''addressed'''
	* Step by Step Query Edit supademo: "Add a space after the "SELECT" claue" should be clause. The error is also in the AI voiceover.		* Under "Step by Step Query Edit" #6 says "you" when it should be "your".
	* Step by Step Query Edit supademo: Two of the slides have the AI voice over saying "Press Pace" instead of "Press Space".		** '''addressed'''
			* Step by Step Query Edit supademo: "Add a space after the "SELECT" claue" should be clause. The error is also in the AI voiceover.
			** '''addressed'''
			* Step by Step Query Edit supademo: Two of the slides have the AI voice over saying "Press Pace" instead of "Press Space".
			** '''addressed'''
	* "How Fields are Populated" second to last bullet point "Data types" should be "Data Types".		* "How Fields are Populated" second to last bullet point "Data types" should be "Data Types".
			** '''addressed'''

	=== Devon 10/22/2025 ===		=== Devon 10/22/2025 ===
	* In the SQL Queries Supademos, the bot reads SQL Query as "S-Q-L Query" and AS Clause as "A-S Clause." It's minor, but I think it would be a good idea to edit the voiceover so the bot reads the terms as how humans would say it. It's jarring to the ear otherwise.		* In the SQL Queries Supademos, the bot reads SQL Query as "S-Q-L Query" and AS Clause as "A-S Clause." It's minor, but I think it would be a good idea to edit the voiceover so the bot reads the terms as how humans would say it. It's jarring to the ear otherwise.

Dsmith at 21:01, 22 October 2025

2025-10-22T21:01:39Z

← Older revision		Revision as of 16:01, 22 October 2025
Line 7:		Line 7:
	* Step by Step Query Edit supademo: Two of the slides have the AI voice over saying "Press Pace" instead of "Press Space".		* Step by Step Query Edit supademo: Two of the slides have the AI voice over saying "Press Pace" instead of "Press Space".
	* "How Fields are Populated" second to last bullet point "Data types" should be "Data Types".		* "How Fields are Populated" second to last bullet point "Data types" should be "Data Types".

			=== Devon 10/22/2025 ===
			* In the SQL Queries Supademos, the bot reads SQL Query as "S-Q-L Query" and AS Clause as "A-S Clause." It's minor, but I think it would be a good idea to edit the voiceover so the bot reads the terms as how humans would say it. It's jarring to the ear otherwise.

Rpatton: Created page with "===Reanna Patton 10/22/2025=== * Where can people go to understand what the Lookup Options do and how to apply it to their use case? ** I now see it's located at the bottom of the page. I would note somewhere that the information will be at the bottom of the page or maybe link to the section in the article. * Under "Test a Database Lookup" what is "appropriate data"? * Under "Step by Step Query Edit" #6 says "you" when it should be "your". * Step by Step Query Edit s..."

2025-10-22T13:51:11Z

Created page with "===Reanna Patton 10/22/2025=== * Where can people go to understand what the Lookup Options do and how to apply it to their use case? ** I now see it's located at the bottom of the page. I would note somewhere that the information will be at the bottom of the page or maybe link to the section in the article. * Under "Test a Database Lookup" what is "appropriate data"? * Under "Step by Step Query Edit" #6 says "you" when it should be "your". * Step by Step Query Edit s..."

New page

===Reanna Patton 10/22/2025===
* Where can people go to understand what the Lookup Options do and how to apply it to their use case?
** I now see it's located at the bottom of the page. I would note somewhere that the information will be at the bottom of the page or maybe link to the section in the article.
* Under "Test a Database Lookup" what is "appropriate data"?
* Under "Step by Step Query Edit" #6 says "you" when it should be "your".
* Step by Step Query Edit supademo: "Add a space after the "SELECT" claue" should be clause. The error is also in the AI voiceover.
* Step by Step Query Edit supademo: Two of the slides have the AI voice over saying "Press Pace" instead of "Press Space".
* "How Fields are Populated" second to last bullet point "Data types" should be "Data Types".