Announcement

Collapse
No announcement yet.

Wish List revisted

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Wish List revisted

    on january 13, 2001, stephane fonteyne in message http://www.powerbasic.com/support/pb...ead.php?t=3086 asked (yet again) for more new features.

    specifically, he asked..

    2. pbcc/pbdll
    -------------
    - buildin [sic] embedded sql code
    on january 15, thierry vanmarcke commented in part:
    i am just wondering, what programs are you writing that you find the features in powerbasic not sufficient enough?
    like asking for embedded sql code???? ...

    well, i've been thinking again: why not embedded sql code?

    i am talking just like the big boys, where you enter:

    Code:
    exec sql begin declare section
      global lastname as asciiz * 255, firstname as asciiz * 255, city as asciiz * 255
    
    end-exec
    (code, presumably more dim statements) 
    exec sql end declare section end-exec
    
    ....
    
        exec sql
         connect to "mydb"
        end-exec
        if sqlcode <> %sqlsuccess  then  ' or sqlstate
         yadda yadda
        else
          exec sql
            declare mycursor cursor for "select * from name_table"
          end exec
          exec sql
            open cursor mycursor
          end-exec
          do while sqlcode = %sqlsuccess
             exec sql
               fetch next mycursor
                 into
                      :lastname, :firstname, :cityname
             end-exec
             if sqlcode = %sqlsuccess then
               call showresult (lastname,firstname, cityname)
             end if
          loop
         end if
    
       etc etc etc.
    ok, if that's not a desireable intrinsic feature, who - besides me - would actually pay for a pb precompiler to translate the exec sql...end-exec stuff into calls to a suitable dll?

    (i do not need the sql "whenever" if that's the hangup)

    good idea, stephane!!




    ------------------
    michael mattias
    racine wi usa
    [email protected]
    Michael Mattias
    Tal Systems Inc. (retired)
    Racine WI USA
    [email protected]
    http://www.talsystems.com

  • #2
    I'll ask R&D to add your name against Stephane's request (aka: 1 tick).

    Thanks!

    ------------------
    Lance
    PowerBASIC Support
    mailto:[email protected][email protected]</A>
    Lance
    mailto:[email protected]

    Comment


    • #3
      I don't understand why people what imbeded SQL! ???

      what's wrong with working with strings? Borland C++ builder and Delphi
      does that and it $#1%'s me! I do a lot of database programming with
      ASP scrips on the front end and all works fine, what's with this stuff?

      You want to give some power to PB databases then give me ADO support!!!
      Everything is MS DBs are going ADO, even Delphi 5 and Borland C++ Building are
      going ADO (admittedly BDE is rubbish though)

      Seeing as this product is only for MS systems shouldn't we consider ADO ??? I like it anyway!


      ------------------

      Paul Dwyer
      Network Engineer
      Aussie in Tokyo
      (Paul282 at VB-World)

      Comment


      • #4
        Ado is bloated, if your wanting ADO just program in VB. SQL such
        as native support for SQL Tools is simple, small and runs without
        a problem. I think that support would be great.

        ------------------
        -Greg
        -Greg
        [email protected]
        MCP,MCSA,MCSE,MCSD

        Comment


        • #5
          To clarify...

          > embedded SQL

          "Embedded SQL", also known as "static SQL", involves hard-coding SQL statements into a program, then (usually) running the program through a pre-compiler that handles all of the SQL stuff. Embedded SQL statements can't be changed at runtime. Embedded SQL is common in COBOL but not in other languages.

          ADO and SQL Tools are not "embedded" techniques. They are much more flexible than that. I'd be very surprised if PowerBASIC ever elected to add true embedded SQL to the language.

          -- Eric Pearson, Perfect Sync Software (suppliers of SQL Tools)


          ------------------
          Perfect Sync: Perfect Sync Development Tools
          Email: mailto:[email protected][email protected]</A>



          [This message has been edited by Eric Pearson (edited January 26, 2001).]
          "Not my circus, not my monkeys."

          Comment


          • #6
            Embedded SQL statements can't be changed at runtime. Embedded SQL is common in COBOL but not in other languages.

            Well, yes and no... I'm glad you added the adjective "true" to "embedded SQL" in your susequent comment, because I was thinking about the kind of embedded SQL where you can change all kinds of stuff at run-time using parameters and dynamic SQL:


            [/quote]

            LET My_Statement = " INSERT INTO foo VALUES ( ?,?,?,?)

            EXEC SQL
            PREPARE :The_statement USING :My_Statement
            END-EXEC
            EXEC SQL
            EXECUTE GLOBAL :The_statement USING "A", :Var_B, :Var_C, :Var_D
            END-EXEC

            [/quote]

            You can also use the table name as a dynamic parameter, although that's not real handy too often as tables seldom have the same column structure.

            Hey, if I'm gonna ask for something, I'm gonna ask for the sky.

            And as you point out, embedded SQL is common in other languages, which is what I like it: I could develop the database access independently from the application, making migration a lot easier.

            MCM
            Michael Mattias
            Tal Systems Inc. (retired)
            Racine WI USA
            [email protected]
            http://www.talsystems.com

            Comment


            • #7
              > And as you point out, embedded SQL is common in other languages,

              Actually what I said was "Embedded SQL is common in COBOL but not in other languages."

              > I could develop the database access independently from the application

              Sounds like ODBC (i.e. SQL Tools) to me! Databases that are ODBC compliant are (more or less) transparent to an ODBC-based system, and since over 50 of the world's most popular databases are ODBC compliant you can "plug in" all those database types without changing your PB/CC or PB/DLL application.

              -- Eric


              ------------------
              Perfect Sync: Perfect Sync Development Tools
              Email: mailto:[email protected][email protected]</A>

              [This message has been edited by Eric Pearson (edited January 26, 2001).]
              "Not my circus, not my monkeys."

              Comment


              • #8
                ODBC-BASIC on PC's <<==>> DB/2 - COBOL on Big Iron.

                Would let me prototype mainframe applications at my home office.

                I admit it: I can't afford an IBM mainframe for myself.

                MCM
                Michael Mattias
                Tal Systems Inc. (retired)
                Racine WI USA
                [email protected]
                http://www.talsystems.com

                Comment

                Working...
                X