Looker Connect Training
Help Center
Documentation
Community
Cloud Certifications
We discussed this at our data services meeting and don’t think we want to go down the road where we have to communicate that everyone has to update their table reference when we make a change. For now, we will use Looker only to prototype a PDT and then move it over into the database. If the information from the hash can be stored somewhere else then the name, then we can use PDTs fully in Looker.
The name is somewhat readable after the hashes. The concern is that the name changes and is impossible to remember with the hashes. Someone would have to look up the table name every time they want to reference it, making it more work and saved queries or dependent views impossible.
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
