Sybase SA 12, 16: Incorrectly selection lines in the code editor

[former_SQLA_member1694881]

Hi All,

Sybase SA 12.0.1.3967 or Sybase SA 16.0.0.1644

In the code editor, such as Sybase ISQL has a line like MYTABLE.MYFIELDNAME.

When you double-click mouse on the side lines (on the MYTABLE or MYFIELDNAME) allocates the entire line as a whole, not just the part of the line on which i clicked the mouse. It turns out that the code editor ignoring delimiters SQL constructs in the allocation line.

Need to fix it.

[former_SQLA_member1694881]

In Sybase SA 12.0.1.4085 this bug is not fixed.

[jeff_albion]

I'm not sure I understand your problem description.

In the code editor, such as Sybase ISQL has a line like MYTABLE.MYFIELDNAME.

Is this the entire line of text you're using?

Here is what I'm trying with the demo database:

Line 1 SELECT * FROM GROUPO.Customers WHERE ID = 665;

When you double-click mouse on the side lines (on the MYTABLE or MYFIELDNAME) allocates the entire line as a whole, not just the part of the line on which i clicked the mouse.

If I click on "GROUPO" or "Customers", I highlight the ["GROUPO"."Customers"] item, not the entire line. If I click the bar on the left gray bar, yes, I select the entire line. This is by design.

Can you explain your problem behaviour further?

[former_SQLA_member1694881]

Problem is as follows:

In ISQL 8.0.3.5594 when I do a double-click on the word "Customers", is allocated only the word "Customers" (see ASA8.jpg).

In ISQL 12.0.1.4085 when I do a double-click on the word "Customers", is allocated two words "GROUPO.Customers" (see ASA12.jpg). I believe that it is not right and I want to correct this error.

[jeff_albion]

Thank you for the explanation.

Unlike other scenarios, I think this is somewhat a matter of opinion of what is the "right thing to do"...

---

So in version 12, there are further enhancements to the SQL syntax for SQL Anywhere. For instance, we introduced SEQUENCES that have the following syntax:

CREATE SEQUENCE DBA.mysequence INCREMENT BY 1;
CREATE TABLE t1 ( c1 INT PRIMARY KEY );
INSERT INTO t1 (c1) VALUES (mysequence.nextval);


If I'm editing in dbisql, I probably do not want to just select the "mysequence" identifier without .nextval (a "dotted expression").
However, if I use any identifier mark in my SQL it is then clear what is supposed to happen and DBISQL will select just the identifier you're selecting:
CREATE SEQUENCE "DBA"."mysequence" INCREMENT BY 1;
CREATE TABLE t1 ( c1 INT );
INSERT INTO t1 (c1) VALUES ("DBA".mysequence.nextval);


Version 16 also introduced the ROW type which uses dotted expressions.

In summary, the SQL you have posted is not clearly an "identifier" or a "dotted expression", so currently you will need to add identifier marks (double-quotes (""), square-brackets ([]) or back quotes (``)) to make it clear what you want dbisql to do.

[former_SQLA_member1694881]

Use (double-quotes (""), square-brackets ([]) or back quotes (``)) not very comfortable. Can I add ISQL setting that would regulate the allocation of the word by double-clicking the mouse: like ASA8 or like SA12 ?