#7328: query Analyzer -->> EOL set to CR -> causes error sql string parsing

ivangron reported 2012-07-31T21:38:58Z · last modified 2012-08-01T23:18:41Z

Dev	ivangron
QA	tariqrahiman

Priority	Low
Complexity	Unknown

Component	Q Analyzer
Version	12.0

if you change Options -> SQL Editor -> Force Write EOL -> CR

then try to execute two sql statements seperated by a GO, example:

select current_bigdatetime()

select current_bigtime()

you will notice that its not parsing the statements correctly.

used sybase ase 15.5

10.168.11.57:5000

user: sa pw: *****

database: master

All Comments (4) Change History

NielsGron 2012-07-31T22:05:54Z

I am thinking that we might remove "CR" as an option. No one uses it and it causes problems for the parsers.

NielsGron 2012-07-31T22:34:00Z

Lets remove CR from the options.

ivangron 2012-07-31T23:42:47Z · (edited)

Removed Enum option CR from ForceWriteEOLProperty.java class and any associations to it...

This means if anyone is currently set to CR, there setting will get changed to Default the next time they load and unload ADS

tariqrahiman 2012-08-01T23:18:41Z

Verified in 12.0.0-dev-151