Talk:Database Lookup (Lookup Specification): Difference between revisions
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..." |
Dgreenwood (talk | contribs) |
||
| (4 intermediate revisions by 3 users not shown) | |||
| 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". | ** '''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. | * 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". | ** '''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. | |||
** '''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". | |||
** '''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". | ||
** '''Randall Kinard 10/28/2025 - addressed''' | |||
=== 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. | |||
** 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". | |||
Latest revision as of 07:45, 30 October 2025
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"?
- Randall Kinard 10/28/2025 - addressed
- Under "Step by Step Query Edit" #6 says "you" when it should be "your".
- 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.
- 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".
- Randall Kinard 10/28/2025 - addressed
- "How Fields are Populated" second to last bullet point "Data types" should be "Data Types".
- Randall Kinard 10/28/2025 - addressed
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.
- 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".