-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Suggestion] Allow selection of only custom columns #135
Comments
I'm not aware of a standard SQL way of doing this. |
@marcscheuner-bfh select top 10 c.* from contact c
join account a ON c.contactid = a.primarycontactid is working. Am I missing something? |
Of course this works - obviously. But this returns all columns from Account and Contact - including those gazillion of system-provided columns like "createdby", "createdon" and so forth. I was hoping Mark C. might have a nifty was of making it possible to get just the custom columns of the entities - those that I have defined / added to the entity - leaving out all the system-provided common columns |
Well no - since this is really a Dynamics / CDS / Dataverse-specific feature, there's nothing in the "base" T-SQL language. Maybe a query hint would work?
or something like this - but again: of course, this would be defining a new feature / extension, since T-SQL itself doesn't know anything about the system-provided vs. custom-defined columns of tables in CDS/Dataverse. |
Instead of a query hint, perhaps an option in the intellisense menu to add 'all custom fields' and it would then write out all the fields the metadata indicates are custom? |
More than once lately, I've wanted to get a
SELECT *
from a table in my CDS - but really only for the custom columns that I've added - leaving out all the default system-created columns.Any chance a feature like that could be implemented? Something like a
SELECT custom.* FROM .....
or whatever syntax makes sense - just a way to get all the custom columns for a table, without having to specify each and every single one of them ....The text was updated successfully, but these errors were encountered: