Issue 118340 - Colour-coding in SQL editor should reflect " vs ' distinction
Summary: Colour-coding in SQL editor should reflect " vs ' distinction
Status: UNCONFIRMED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOO330m20
Hardware: All Mac OS X 10
: P3 Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-26 00:34 UTC by ameliab
Modified: 2013-02-07 22:35 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description ameliab 2011-07-26 00:34:08 UTC 
This is a suggestion for minor -- but hopefully easy to implement -- enhancement to improve user-friendliness of the OO database SQL editor.

The editor colour-codes syntax, but it codes double-quoted strings and single-quoted strings the same colour.  In SQL, the two types of quotes have very different meanings -- double quotes are used for names of tables or columns, single quotes are used for literals.  It's easy to mistakenly use the wrong type, and having them show up as different colours would make it easier to catch those mistakes.

********
Just arbitrarily including the American spelling so it will show up in searches: color, color-coding
Comment 1 Oliver-Rainer Wittmann 2012-06-13 12:19:12 UTC 
getting rid of value "enhancement" for field "severity".
For enhancement the field "issue type" shall be used.