Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upCannot create VIEW on MSSQL #39
Comments
This comment has been minimized.
This comment has been minimized.
The view editor in HeidiSQL does currently not care for other systems but MySQL/MariaDB. I guess the controls (definer, sql security, algorithm and check option) are not applicable to a view in MSSQL, or? Is there some good documentation on how to read and write views in MSSQL? |
This comment has been minimized.
This comment has been minimized.
https://docs.microsoft.com/en-us/sql/t-sql/statements/create-view-transact-sql |
This comment has been minimized.
This comment has been minimized.
@ansgarbecker Similar issue with editing an existing view: Hit "Save" and receive an error:
Literally all we need for MS SQL is to ignore the header options so the command sent is simply ALTER VIEW ... Server: MS SQL 2008 R2 |
This comment has been minimized.
This comment has been minimized.
@ansgarbecker Creating and Editing views in MSSQL is actually really simple and used to work in HeidiSQL before one of the updates (don't remember which exactly.) but the crux is that the algorhitm and definer/invoker parts don't work with mssql. Best would be if you could turn these off so the generated syntax would just be "CREATE VIEW [schema_name.]view_name AS
|
This comment has been minimized.
This comment has been minimized.
Hi @ansgarbecker , is there an update on this bug? |
This comment has been minimized.
This comment has been minimized.
Not yet, but if it's really just that I have to remove the mentioned clauses, I can try to get this done for the next release. |
This comment has been minimized.
This comment has been minimized.
I would say removing the extra clauses would resolve the bug. If anybody
needs any extra functionality related to the MS SQL specific CREATE VIEW
statement. Then they can open that up as a feature request or enhancement
…On Tue, Oct 8, 2019 at 7:07 AM Ansgar Becker ***@***.***> wrote:
Not yet, but if it's really just that I have to remove the mentioned
clauses, I can try to get this done for the next release.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#39?email_source=notifications&email_token=ABZDR3OEEGRQHQ47UFMKRKLQNRZYDA5CNFSM4EHYG6WKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAT5PII#issuecomment-539482017>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABZDR3N3F22JFASVTCDYRIDQNRZYDANCNFSM4EHYG6WA>
.
|
Current behavior
When creating a view on MS SQL 11.0 DB, algorithm is set to undefined, but instead of ignoring algorithm in the create statement, it still leaves "ALGORITHM = UNDEFINED" at the beginning of the create. The entire Alg section should be unavailable/grayed out as well for a MSSQL connection.
Failure information (for bugs)
/* SQL Error (343): Unknown object type 'ALGORITHM' used in a CREATE, DROP, or ALTER statement. */
Steps to reproduce
Please provide detailed steps for reproducing the issue.
Context
Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.