I just wanted to report a bug with the syntax highlighting inside SQL.
Not sure if anyone is aware of it yet or not. I've uploaded a sample
file to the Google group, and I've uploaded a screenshot showing my
issue.
Basically it looks like the issue is that after surrounding something
with pounds (sharps, #, or whatever you like to call it) in a SQL
query the rest of the line is commented out. Are pounds comments in
some SQL variants?
Anyway, I just thought it'd take a second and report it.
Title : i just wanted to report a bug with the syntax highlighting
inside sql
TicId : 193131bea5058bac812029b64de3d39e0e9799cb
Assigned : anon
Opened : Wed Apr 01 08:06:25 +1100 2009 (0 days)
State : OPEN
Tags : syntax-sql
Comments (1):
* Added 04/01 08:06 by anon
Not sure if anyone is aware of it yet or not. I've uploaded a sample
file to the Google group, and I've uploaded a screenshot showing my
issue.
> I just wanted to report a bug with the syntax highlighting inside SQL.
> Not sure if anyone is aware of it yet or not. I've uploaded a sample
> file to the Google group, and I've uploaded a screenshot showing my
> issue.
> Basically it looks like the issue is that after surrounding something
> with pounds (sharps, #, or whatever you like to call it) in a SQL
> query the rest of the line is commented out. Are pounds comments in
> some SQL variants?
> Anyway, I just thought it'd take a second and report it.
Noticed another problem. See the attached. The comment on line 3 should be
formatted like the comment on line 5. It seems to happen because of the "id"
variable on line 2 being set to another variable versus something withing
quotes. Couple things I noticed that might help debug it:
- Setting anything ending with "id" will create the problem so "myobj.id"
also does it.
- Using quotes on the right side will bypass the problem.
- Once the problem happens on line 2 then any variable set to another
variable after that will also cause comments after them to lose their
formatting, until quotes show up.
> Title : i just wanted to report a bug with the syntax highlighting
> inside sql
> TicId : 193131bea5058bac812029b64de3d39e0e9799cb
> Assigned : anon
> Opened : Wed Apr 01 08:06:25 +1100 2009 (0 days)
> State : OPEN
> Tags : syntax-sql
> Comments (1):
> * Added 04/01 08:06 by anon
> Not sure if anyone is aware of it yet or not. I've uploaded a
> sample
> file to the Google group, and I've uploaded a screenshot showing my
> issue.
> On Apr 1, 2009, at 7:40 AM, Daniel Jimenez wrote:
> > Hi all,
> > I just wanted to report a bug with the syntax highlighting inside SQL.
> > Not sure if anyone is aware of it yet or not. I've uploaded a sample
> > file to the Google group, and I've uploaded a screenshot showing my
> > issue.
> > Basically it looks like the issue is that after surrounding something
> > with pounds (sharps, #, or whatever you like to call it) in a SQL
> > query the rest of the line is commented out. Are pounds comments in
> > some SQL variants?
> > Anyway, I just thought it'd take a second and report it.
Title : the comment on line 3 should be formatted like the comment
on line 5 it seems to happen because of the id variable on line 2
being set to another variable versus something withing quotes couple
things i noticed that might help debug it
TicId : 21eb0ab98fff40693fa3efb8bd1be9f31335e4d2
Assigned : anon
Opened : Wed Apr 08 09:27:47 +1000 2009 (0 days)
State : OPEN
Tags : syntax-variable-comment-colour
Comments (1):
* Added 04/08 09:27 by anon
- Setting anything ending with "id" will create the problem so
"myobj.id" also
does it.
- Using quotes on the right side will bypass the problem.
- Once the problem happens on line 2 then any variable set to another
variable
after that will also cause comments after them to lose their
formatting, until
** more... **
> Noticed another problem. See the attached. The comment on line 3
> should be formatted like the comment on line 5. It seems to happen
> because of the "id" variable on line 2 being set to another variable
> versus something withing quotes. Couple things I noticed that might
> help debug it:
> - Setting anything ending with "id" will create the problem so
> "myobj.id" also does it.
> - Using quotes on the right side will bypass the problem.
> - Once the problem happens on line 2 then any variable set to
> another variable after that will also cause comments after them to
> lose their formatting, until quotes show up.
> - Andrew
> On Tue, Mar 31, 2009 at 5:07 PM, Rob Rohan <robro...@gmail.com> wrote:
> Thanks Daniel, I'll see what I can see (if no one beats me to it)
> Title : i just wanted to report a bug with the syntax highlighting
> inside sql
> TicId : 193131bea5058bac812029b64de3d39e0e9799cb
> Assigned : anon
> Opened : Wed Apr 01 08:06:25 +1100 2009 (0 days)
> State : OPEN
> Tags : syntax-sql
> Comments (1):
> * Added 04/01 08:06 by anon
> Not sure if anyone is aware of it yet or not. I've uploaded a
> sample
> file to the Google group, and I've uploaded a screenshot
> showing my
> issue.
> On Apr 1, 2009, at 7:40 AM, Daniel Jimenez wrote:
> > Hi all,
> > I just wanted to report a bug with the syntax highlighting inside
> SQL.
> > Not sure if anyone is aware of it yet or not. I've uploaded a sample
> > file to the Google group, and I've uploaded a screenshot showing my
> > issue.
> > Basically it looks like the issue is that after surrounding
> something
> > with pounds (sharps, #, or whatever you like to call it) in a SQL
> > query the rest of the line is commented out. Are pounds comments in
> > some SQL variants?
> > Anyway, I just thought it'd take a second and report it.
For the (seemingly) amount of traction cftextmate has I'm surprised
more people haven't reported this. Is anyone "formally" supporting
cftextmate via www.cftextmate.com? It'll be great when this issue
(vars rendering as comments inside cfquery) is fixed!
Thanks for the hard work!
Dylan
On Mar 31, 2:07 pm, Rob Rohan <robro...@gmail.com> wrote:
> Title : i just wanted to report a bug with the syntax highlighting
> inside sql
> TicId : 193131bea5058bac812029b64de3d39e0e9799cb
> Assigned : anon
> Opened : Wed Apr 01 08:06:25 +1100 2009 (0 days)
> State : OPEN
> Tags : syntax-sql
> Comments (1):
> * Added 04/01 08:06 by anon
> Not sure if anyone is aware of it yet or not. I've uploaded a sample
> file to the Google group, and I've uploaded a screenshot showing my
> issue.
> On Apr 1, 2009, at 7:40 AM, Daniel Jimenez wrote:
> > Hi all,
> > I just wanted to report a bug with the syntax highlighting inside SQL.
> > Not sure if anyone is aware of it yet or not. I've uploaded a sample
> > file to the Google group, and I've uploaded a screenshot showing my
> > issue.
> > Basically it looks like the issue is that after surrounding something
> > with pounds (sharps, #, or whatever you like to call it) in a SQL
> > query the rest of the line is commented out. Are pounds comments in
> > some SQL variants?
> > Anyway, I just thought it'd take a second and report it.
> For the (seemingly) amount of traction cftextmate has I'm surprised
> more people haven't reported this. Is anyone "formally" supporting
> cftextmate via www.cftextmate.com? It'll be great when this issue
> (vars rendering as comments inside cfquery) is fixed!
> Thanks for the hard work!
> Dylan
> On Mar 31, 2:07 pm, Rob Rohan <robro...@gmail.com> wrote:
>> Thanks Daniel, I'll see what I can see (if no one beats me to it)
>> Title : i just wanted to report a bug with the syntax
>> highlighting
>> inside sql
>> TicId : 193131bea5058bac812029b64de3d39e0e9799cb
>> Assigned : anon
>> Opened : Wed Apr 01 08:06:25 +1100 2009 (0 days)
>> State : OPEN
>> Tags : syntax-sql
>> Comments (1):
>> * Added 04/01 08:06 by anon
>> Not sure if anyone is aware of it yet or not. I've uploaded
>> a sample
>> file to the Google group, and I've uploaded a screenshot
>> showing my
>> issue.
>> On Apr 1, 2009, at 7:40 AM, Daniel Jimenez wrote:
>>> Hi all,
>>> I just wanted to report a bug with the syntax highlighting inside
>>> SQL.
>>> Not sure if anyone is aware of it yet or not. I've uploaded a sample
>>> file to the Google group, and I've uploaded a screenshot showing my
>>> issue.
>>> Basically it looks like the issue is that after surrounding
>>> something
>>> with pounds (sharps, #, or whatever you like to call it) in a SQL
>>> query the rest of the line is commented out. Are pounds comments in
>>> some SQL variants?
>>> Anyway, I just thought it'd take a second and report it.