On 2015-01-28 15:27, Paul wrote: > I'm editing a file tmp.sql with syntax colouring. The following > code all turns yellow after the first double quote (actual file > contains a lot more code). I'm in an environment, where upgrading > anything is difficult. Is there anything superficial changes I can > make to prevent this unexpected colour behaviour? > > SELECT > Field1, > COUNT(*) AS Field2, > MIN ( LEN( REPLACE( EEEPppp, "\", "" ) ) ) AS Field3, > FROM someTable > etc....
I'd expect that, as I believe just about every SQL engine out there uses ANSI-standard single-quotes instead of double-quotes. Some might *permit* double-quoted strings, but it certainly doesn't adhere to standards, and double-quotes are used in some databases to quote names of databases/tables/columns. What SQL engine is this for? -tim -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
