-
Notifications
You must be signed in to change notification settings - Fork 14
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
Skip read-only columns #27
Comments
Interesting idea. I'll think about the best way to do this. |
@gatuser I'm intending to include an options dialog in the next release. Among the options will be a dropdown for how to handle read-only fields. For ROWVERSION/TIMESTAMP:
There will be two checkboxes to enable scripting of Identity and Computed fields. By default they will be "on". |
Sounds good… Just as an FYI, I would use this tool mainly to script out existing tables/data in order to be able to create the table and insert data into another database. Usually for small and mainly static tables that would be used to support an application I would be developing. For that reason, the table I am inserting into would be the same as was scripted using your tool and I would never be wanting to insert into any read-only columns. From: Steve Ognibene [mailto:notifications@github.com] @gatuser https://github.com/gatuser I'm intending to include an options dialog in the next release. Among the options will be a dropdown for how to handle read-only fields. For ROWVERSION/TIMESTAMP: "In SQL Server, you can't insert an explicit value in a ROWVERSION or TIMESTAMP field" There will be two checkboxes to enable scripting of Identity and Computed fields. By default they will be "on". — |
It would be nice if when you say Select * from a table, it would not include read-only columns. E.g., timestamp, identity, computed columns. Thanks.
The text was updated successfully, but these errors were encountered: