| Summary: | [syntax] Syntax styling for SQL doesn't consider implementation specific keywords | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Curtis Windatt <curtis.windatt.public> |
| Component: | Client | Assignee: | Grant Gayed <grant_gayed> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | minor | ||
| Priority: | P3 | ||
| Version: | 12.0 | ||
| Target Milestone: | 13.0 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
SQL Server and other SQL implementations use additional keywords that are not marked. The behaviour of the CREATE highlighting means that CREATE is not considered a keyword in these cases. CREATE FUNCTION to_dms( degrees DOUBLE ) CREATE SCHEMA "Trading"; CREATE STREAM "Orders" In all these cases CREATE is not marked as a keyword. Simple fix would be to remove the requirement that CREATE is followed by DATABASE or TABLE. Also CONTAINS is a SQL Server specific keyword CONTAINS ( { column_name | ( column_list ) | * | PROPERTY ( { column_name }, 'property_name' ) } , '<contains_search_condition>' [ , LANGUAGE language_term ] ) SELECT * FROM table WHERE CONTAINS(Column, 'test');