[jira] [Commented] (DERBY-693) Incorrect line number in the error message when parser throws syntax error in some specific examples

2016-10-13 Thread Leshan Bashitha Wijegunawardana (JIRA)

[ 
https://issues.apache.org/jira/browse/DERBY-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15574047#comment-15574047
 ] 

Leshan Bashitha Wijegunawardana commented on DERBY-693:
---

Bryan, I tried with commenting all the line incrementing parts with the 'line' 
field. But it doesn't give any change for the line number in the error message 
giving. Error message is giving always at line 2 for the second select. I tried 
with giving '0' for the line field in the class which is originally given as 
line = 1. But then also no change. I hope that line number is incrementing 
wrongly is not directly in this piece of code. 

> Incorrect line number in the error message when parser throws syntax error in 
> some specific examples
> 
>
> Key: DERBY-693
> URL: https://issues.apache.org/jira/browse/DERBY-693
> Project: Derby
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 10.2.1.6
>Reporter: Mamta A. Satoor
>Assignee: Leshan Bashitha Wijegunawardana
>Priority: Minor
>  Labels: derby_triage10_5_2
> Attachments: w.sql
>
>
> After connecting to a database through ij, parser returns correct line number 
> for the sql "select" the first time around but it returns incorrect line 
> number when the same sql is rexecuted, as shown below
> $ java org.apache.derby.tools.ij
> ij version 10.2
> ij> connect 'jdbc:derby:c:/dellater/db1';
> ij> select
> ;
> ERROR 42X01: Syntax error: Encountered "" at line 1, column 8.
> ij> select
> ;
> ERROR 42X01: Syntax error: Encountered "" at line 2, column 8.
> ij>
> This is caused by UCode_CharStream's UpdateLineColumn method. When the sql 
> "select" is executed the first time, the parser comes to UpdateLineColumn 
> method for trailing \r and then for trailing \n for the first line "select". 
> The trailing \n causes the prevCharIsLF to be set to true. Since this sql is 
> incorrect by itself, parser will throw a syntax error. After the exception 
> and before the processing of next sql "select", this prevCharIsLF flag does 
> not get set to false(this is the problem). When the first character "s" is 
> read, UpdateLineColumn checks if prevCharIsLF set to true and if yes, it 
> increments(incorrectly) the line number to 2 and that is why the second time 
> around, execution of "select" gives syntax error at line 2 rather than line 1.
> This also causes problem with the optimizer hints when they are used in 
> incorrect context as shown below. 
> $ java org.apache.derby.tools.ij
> ij version 10.2
> ij> connect 'jdbc:derby:c:/dellater/db1';
> ij> -- derby-properties
> select * from t1;
> ERROR 42X01: Syntax error: Encountered "derby-properties" at line 1, column 4.
> ij> -- derby-properties
> select * from t1;
> ERROR 42X01: Syntax error: Encountered "derby-properties" at line 2, column 4.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (DERBY-693) Incorrect line number in the error message when parser throws syntax error in some specific examples

2016-08-27 Thread Bryan Pendleton (JIRA)

[ 
https://issues.apache.org/jira/browse/DERBY-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15441880#comment-15441880
 ] 

Bryan Pendleton commented on DERBY-693:
---

OK, that is good analysis and good to know.

Sometimes, our first guess about the source of the problem is wrong.

We will have to look some more.

I see that the UCode_CharStream class also contains the interesting methods 
"adjustBeginLineColumn()" and "ReInit()". Perhaps one of those methods is being 
called, and is altering the line number unexpectedly?

Perhaps you can instrument each of the places where the 'line' field of the 
class is being changed, and observe how the changes occur, when you run the 
reproduction script?


> Incorrect line number in the error message when parser throws syntax error in 
> some specific examples
> 
>
> Key: DERBY-693
> URL: https://issues.apache.org/jira/browse/DERBY-693
> Project: Derby
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 10.2.1.6
>Reporter: Mamta A. Satoor
>Assignee: Leshan Bashitha Wijegunawardana
>Priority: Minor
>  Labels: derby_triage10_5_2
> Attachments: w.sql
>
>
> After connecting to a database through ij, parser returns correct line number 
> for the sql "select" the first time around but it returns incorrect line 
> number when the same sql is rexecuted, as shown below
> $ java org.apache.derby.tools.ij
> ij version 10.2
> ij> connect 'jdbc:derby:c:/dellater/db1';
> ij> select
> ;
> ERROR 42X01: Syntax error: Encountered "" at line 1, column 8.
> ij> select
> ;
> ERROR 42X01: Syntax error: Encountered "" at line 2, column 8.
> ij>
> This is caused by UCode_CharStream's UpdateLineColumn method. When the sql 
> "select" is executed the first time, the parser comes to UpdateLineColumn 
> method for trailing \r and then for trailing \n for the first line "select". 
> The trailing \n causes the prevCharIsLF to be set to true. Since this sql is 
> incorrect by itself, parser will throw a syntax error. After the exception 
> and before the processing of next sql "select", this prevCharIsLF flag does 
> not get set to false(this is the problem). When the first character "s" is 
> read, UpdateLineColumn checks if prevCharIsLF set to true and if yes, it 
> increments(incorrectly) the line number to 2 and that is why the second time 
> around, execution of "select" gives syntax error at line 2 rather than line 1.
> This also causes problem with the optimizer hints when they are used in 
> incorrect context as shown below. 
> $ java org.apache.derby.tools.ij
> ij version 10.2
> ij> connect 'jdbc:derby:c:/dellater/db1';
> ij> -- derby-properties
> select * from t1;
> ERROR 42X01: Syntax error: Encountered "derby-properties" at line 1, column 4.
> ij> -- derby-properties
> select * from t1;
> ERROR 42X01: Syntax error: Encountered "derby-properties" at line 2, column 4.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (DERBY-693) Incorrect line number in the error message when parser throws syntax error in some specific examples

2016-08-22 Thread Leshan Bashitha Wijegunawardana (JIRA)

[ 
https://issues.apache.org/jira/browse/DERBY-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15431456#comment-15431456
 ] 

Leshan Bashitha Wijegunawardana commented on DERBY-693:
---

Bryan, I did all the above mentioned steps. But it didn't resolve. When the sql 
command("select") is executed prevCharIsLF flag is set to true in both the 
occasions even without modification to the code. In both the occasions 
UpdateLineColumn method is called and the code within the if block(which is 
checking prevCharIsLF is true ) is executed. (incrementing line number is also 
here) But for the surprise when giving the error message line number is given 
as in the description every time. When I did the modification mentioned above 
(prevCharIsLF is set to false before calling UpdateLineColumn method in 
readChar method) , since prevCharIsLF is set to false the code within the if 
block is not executed which means that incrementing line number is also not 
executed. But even after that also the error message is as above. And also even 
after commenting the line incrementing part also gives the error message as in 
the description. So it seems like incrementing line number incorrectly happens 
not within the code which is in the description. 

> Incorrect line number in the error message when parser throws syntax error in 
> some specific examples
> 
>
> Key: DERBY-693
> URL: https://issues.apache.org/jira/browse/DERBY-693
> Project: Derby
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 10.2.1.6
>Reporter: Mamta A. Satoor
>Assignee: Leshan Bashitha Wijegunawardana
>Priority: Minor
>  Labels: derby_triage10_5_2
> Attachments: w.sql
>
>
> After connecting to a database through ij, parser returns correct line number 
> for the sql "select" the first time around but it returns incorrect line 
> number when the same sql is rexecuted, as shown below
> $ java org.apache.derby.tools.ij
> ij version 10.2
> ij> connect 'jdbc:derby:c:/dellater/db1';
> ij> select
> ;
> ERROR 42X01: Syntax error: Encountered "" at line 1, column 8.
> ij> select
> ;
> ERROR 42X01: Syntax error: Encountered "" at line 2, column 8.
> ij>
> This is caused by UCode_CharStream's UpdateLineColumn method. When the sql 
> "select" is executed the first time, the parser comes to UpdateLineColumn 
> method for trailing \r and then for trailing \n for the first line "select". 
> The trailing \n causes the prevCharIsLF to be set to true. Since this sql is 
> incorrect by itself, parser will throw a syntax error. After the exception 
> and before the processing of next sql "select", this prevCharIsLF flag does 
> not get set to false(this is the problem). When the first character "s" is 
> read, UpdateLineColumn checks if prevCharIsLF set to true and if yes, it 
> increments(incorrectly) the line number to 2 and that is why the second time 
> around, execution of "select" gives syntax error at line 2 rather than line 1.
> This also causes problem with the optimizer hints when they are used in 
> incorrect context as shown below. 
> $ java org.apache.derby.tools.ij
> ij version 10.2
> ij> connect 'jdbc:derby:c:/dellater/db1';
> ij> -- derby-properties
> select * from t1;
> ERROR 42X01: Syntax error: Encountered "derby-properties" at line 1, column 4.
> ij> -- derby-properties
> select * from t1;
> ERROR 42X01: Syntax error: Encountered "derby-properties" at line 2, column 4.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (DERBY-693) Incorrect line number in the error message when parser throws syntax error in some specific examples

2016-08-04 Thread Bryan Pendleton (JIRA)

[ 
https://issues.apache.org/jira/browse/DERBY-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15408690#comment-15408690
 ] 

Bryan Pendleton commented on DERBY-693:
---

I think you're definitely looking at the right code.

I encourage you to test your theory about a possible fix:

1) First, run the IJ statements as described in the bug description, so that
   you can see the behavior that happens

2) Next, try making the change that you think will fix it

3) Then, try the same IJ experiment, with your modified code. Does it
   resolve the problem?

Let us know what you see when you make these experiments.

> Incorrect line number in the error message when parser throws syntax error in 
> some specific examples
> 
>
> Key: DERBY-693
> URL: https://issues.apache.org/jira/browse/DERBY-693
> Project: Derby
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 10.2.1.6
>Reporter: Mamta A. Satoor
>Assignee: Leshan Bashitha Wijegunawardana
>Priority: Minor
>  Labels: derby_triage10_5_2
> Attachments: w.sql
>
>
> After connecting to a database through ij, parser returns correct line number 
> for the sql "select" the first time around but it returns incorrect line 
> number when the same sql is rexecuted, as shown below
> $ java org.apache.derby.tools.ij
> ij version 10.2
> ij> connect 'jdbc:derby:c:/dellater/db1';
> ij> select
> ;
> ERROR 42X01: Syntax error: Encountered "" at line 1, column 8.
> ij> select
> ;
> ERROR 42X01: Syntax error: Encountered "" at line 2, column 8.
> ij>
> This is caused by UCode_CharStream's UpdateLineColumn method. When the sql 
> "select" is executed the first time, the parser comes to UpdateLineColumn 
> method for trailing \r and then for trailing \n for the first line "select". 
> The trailing \n causes the prevCharIsLF to be set to true. Since this sql is 
> incorrect by itself, parser will throw a syntax error. After the exception 
> and before the processing of next sql "select", this prevCharIsLF flag does 
> not get set to false(this is the problem). When the first character "s" is 
> read, UpdateLineColumn checks if prevCharIsLF set to true and if yes, it 
> increments(incorrectly) the line number to 2 and that is why the second time 
> around, execution of "select" gives syntax error at line 2 rather than line 1.
> This also causes problem with the optimizer hints when they are used in 
> incorrect context as shown below. 
> $ java org.apache.derby.tools.ij
> ij version 10.2
> ij> connect 'jdbc:derby:c:/dellater/db1';
> ij> -- derby-properties
> select * from t1;
> ERROR 42X01: Syntax error: Encountered "derby-properties" at line 1, column 4.
> ij> -- derby-properties
> select * from t1;
> ERROR 42X01: Syntax error: Encountered "derby-properties" at line 2, column 4.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (DERBY-693) Incorrect line number in the error message when parser throws syntax error in some specific examples

2016-08-03 Thread Amelia Garripoli (JIRA)

[ 
https://issues.apache.org/jira/browse/DERBY-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15407146#comment-15407146
 ] 

Amelia Garripoli commented on DERBY-693:


Thank you for your email. This is an automated reply. I don't work during 
summer term and will be available again on September 2, 2016.

If you are seeking advising, please contact the Advising & Counseling Center, 
Room HSS-203G on the Bremerton campus. The primary Entry Advisor for all CIS 
programs is Steve Quinn (squ...@olympic.edu). To make an advising appointment 
contact him directly or call the Advising & Counseling Center at 360-475-7530. 
Additional information about CIS programs and the BAS-IS program can be found 
at the CIS "Digital Advisor" at 
http://cis2.oc.ctc.edu/oc_apps/CIS/da/cisadvisor.php

If you need immediate assistance on anything else, please contact the Business 
& Technology division office at 360-475-7360.

See you in September,
~Amelia.

Amelia Garripoli, Professor, Information Systems
Olympic College, 1600 Chester Avenue, Bremerton, WA  98337
agarrip...@olympic.edu, (360) 475-7588, TEC-210
http://faculty.olympic.edu/agarripoli
See OC's Bachelor of Applied Science in Information Systems (BAS IS)

---
"A world without string is chaos." ~ Rudolf Smuntz, MouseHunt


> Incorrect line number in the error message when parser throws syntax error in 
> some specific examples
> 
>
> Key: DERBY-693
> URL: https://issues.apache.org/jira/browse/DERBY-693
> Project: Derby
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 10.2.1.6
>Reporter: Mamta A. Satoor
>Priority: Minor
>  Labels: derby_triage10_5_2
> Attachments: w.sql
>
>
> After connecting to a database through ij, parser returns correct line number 
> for the sql "select" the first time around but it returns incorrect line 
> number when the same sql is rexecuted, as shown below
> $ java org.apache.derby.tools.ij
> ij version 10.2
> ij> connect 'jdbc:derby:c:/dellater/db1';
> ij> select
> ;
> ERROR 42X01: Syntax error: Encountered "" at line 1, column 8.
> ij> select
> ;
> ERROR 42X01: Syntax error: Encountered "" at line 2, column 8.
> ij>
> This is caused by UCode_CharStream's UpdateLineColumn method. When the sql 
> "select" is executed the first time, the parser comes to UpdateLineColumn 
> method for trailing \r and then for trailing \n for the first line "select". 
> The trailing \n causes the prevCharIsLF to be set to true. Since this sql is 
> incorrect by itself, parser will throw a syntax error. After the exception 
> and before the processing of next sql "select", this prevCharIsLF flag does 
> not get set to false(this is the problem). When the first character "s" is 
> read, UpdateLineColumn checks if prevCharIsLF set to true and if yes, it 
> increments(incorrectly) the line number to 2 and that is why the second time 
> around, execution of "select" gives syntax error at line 2 rather than line 1.
> This also causes problem with the optimizer hints when they are used in 
> incorrect context as shown below. 
> $ java org.apache.derby.tools.ij
> ij version 10.2
> ij> connect 'jdbc:derby:c:/dellater/db1';
> ij> -- derby-properties
> select * from t1;
> ERROR 42X01: Syntax error: Encountered "derby-properties" at line 1, column 4.
> ij> -- derby-properties
> select * from t1;
> ERROR 42X01: Syntax error: Encountered "derby-properties" at line 2, column 4.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (DERBY-693) Incorrect line number in the error message when parser throws syntax error in some specific examples

2016-08-03 Thread Leshan Bashitha Wijegunawardana (JIRA)

[ 
https://issues.apache.org/jira/browse/DERBY-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15407143#comment-15407143
 ] 

Leshan Bashitha Wijegunawardana commented on DERBY-693:
---

I'm a computer engineering undergraduate who is new to the Apache Derby code 
base. According to the explanation here I understood that this issue can be 
overcome by setting  prevCharIsLF flag to false before calling UpdateLineColumn 
method. When I go through the UCode_CharStream class there is one place that 
the UpdateLineColumn method is called. That is in the readChar method. So I 
hope this can be overcome by setting prevCharIsLF flag to false before calling 
UpdateLineColumn method in the readChar method. Is that ok? Else can anyone 
explain me the issue liittle bit. 
Thanks. 

> Incorrect line number in the error message when parser throws syntax error in 
> some specific examples
> 
>
> Key: DERBY-693
> URL: https://issues.apache.org/jira/browse/DERBY-693
> Project: Derby
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 10.2.1.6
>Reporter: Mamta A. Satoor
>Priority: Minor
>  Labels: derby_triage10_5_2
> Attachments: w.sql
>
>
> After connecting to a database through ij, parser returns correct line number 
> for the sql "select" the first time around but it returns incorrect line 
> number when the same sql is rexecuted, as shown below
> $ java org.apache.derby.tools.ij
> ij version 10.2
> ij> connect 'jdbc:derby:c:/dellater/db1';
> ij> select
> ;
> ERROR 42X01: Syntax error: Encountered "" at line 1, column 8.
> ij> select
> ;
> ERROR 42X01: Syntax error: Encountered "" at line 2, column 8.
> ij>
> This is caused by UCode_CharStream's UpdateLineColumn method. When the sql 
> "select" is executed the first time, the parser comes to UpdateLineColumn 
> method for trailing \r and then for trailing \n for the first line "select". 
> The trailing \n causes the prevCharIsLF to be set to true. Since this sql is 
> incorrect by itself, parser will throw a syntax error. After the exception 
> and before the processing of next sql "select", this prevCharIsLF flag does 
> not get set to false(this is the problem). When the first character "s" is 
> read, UpdateLineColumn checks if prevCharIsLF set to true and if yes, it 
> increments(incorrectly) the line number to 2 and that is why the second time 
> around, execution of "select" gives syntax error at line 2 rather than line 1.
> This also causes problem with the optimizer hints when they are used in 
> incorrect context as shown below. 
> $ java org.apache.derby.tools.ij
> ij version 10.2
> ij> connect 'jdbc:derby:c:/dellater/db1';
> ij> -- derby-properties
> select * from t1;
> ERROR 42X01: Syntax error: Encountered "derby-properties" at line 1, column 4.
> ij> -- derby-properties
> select * from t1;
> ERROR 42X01: Syntax error: Encountered "derby-properties" at line 2, column 4.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)