Concatenation operator in embedded SQL statements in 4GL

Concatenation operator in embedded SQL statements in 4GL

Post by Jacob Salomo » Sun, 31 Dec 1899 09:00:00



Hi Family,

I just tried the following in a 4GL program:

        select col1 || col2
  into myvariable
  from some_table

The 4GL compiler actually generated a syntax error for this! >;-(  I had
to go through the PREPARE/DECLARE/OPEN/FETCH rigmarole.

Considering that the || concatenation operator has been available in the
engine since 4.1 or so, I find it incredible that the 4GL 6.05 syntax
checker can't handle it.

Anyone know if this is a known bug? Or some outstanding feature request?
It certainly was not expected behavior!

Thanks.

--
    -- Jake (In pursuit of undomesticated aquatic avians)

+----------------------------------------------------------+
|Aside from that, how did you enjoy the play, Mrs. Lincoln?|
+----------------------------------------------------------+

 
 
 

Concatenation operator in embedded SQL statements in 4GL

Post by David William » Sun, 31 Dec 1899 09:00:00




Quote:>Hi Family,

>I just tried the following in a 4GL program:

>       select col1 || col2
>  into myvariable
>  from some_table

>The 4GL compiler actually generated a syntax error for this! >;-(  I had
>to go through the PREPARE/DECLARE/OPEN/FETCH rigmarole.

>Considering that the || concatenation operator has been available in the
>engine since 4.1 or so, I find it incredible that the 4GL 6.05 syntax
>checker can't handle it.

  That's true - it is not valid syntax.

Quote:>Anyone know if this is a known bug? Or some outstanding feature request?

  Not a bug and probably not a feature request....after all 4GL has full
  variable handling i.e. is a full programming langague.

Quote:>It certainly was not expected behavior!

>Thanks.

--
David Williams

 
 
 

1. Concatenation operator in embedded SQL statements in 4GL

Jake,

I ran into the same problem a few months back. When I called tech support
they told me that was the way it was designed to behave and not a bug.
(I have version 6.00). They also mentioned that there were no plans to
change it to work. So I guess we will just have to do the prepares/declares/
open/fetch/close/free stuff every time we want to concatonate something.

---
            ,-, |~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|  =======
         ___||  |                                              |  -----
        //_ ||  |      CANNON EXPRESS                          | ----
 ,-----'| ~  |  |                                              |      --
 |o-----|__  |--`======_______________________________======___| ~~~~~~~~
 `-(*)--===~~~~~~(*)(*)|                              (*)(*)|  -------
-------------------------------------------------------------------------

PO Box 364                  |opinions express are those of my own and
Springdale, AR 72764 USA    |don't necessarily reflect those of my company
-------------------------------------------------------------------------

2. Why oh why doesn't this work?

3. Concatenation Operator in 4GL

4. ADO in IDL file

5. SPL/SQL Concatenation Operator

6. odbc3 stored procedure call output parameter problem

7. String Concatenation Operator changed functionality in 7.0

8. Optimal SQL query needed

9. Concatenation Operator: Is this a bug?

10. Bug in concatenation Operator ?

11. Loosing a space when using the concatenation operator in Ingres 4 GL