Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Why does AA not support arguments directly in field SELECT statement?

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

  • Why does AA not support arguments directly in field SELECT statement?

    Why is it that AA does not fully support putting SQL Arguments into SELECT portion of a SQL statement?

    Over and over, I have found it would be extremely convenient if I could place a SQL argument directly into the SELECT clause of fields either in an "IF" expression or directly as a column to be returned.

    There are two scenarios where this always crops up for me:
    1) letting SQL be aware of the current logged in user, so it can perform security related processing or so it can echo back security values for client-side processing,
    2) letting SQL be aware of a particular column value from a grandparent table that is not involved directly in the query, especially when using the Nested SQL Genie builder. The grandparent table can be joined into a second level query, but it seems wasteful to do so, when the grandparent table values are already known way ahead of time (before the top level query is even run!) and could be passed in as arguments to be used in the SELECT clause directly as returned values or in "IF" statements.

  • #2
    Re: Why does AA not support arguments directly in field SELECT statement?

    Could you write some pseudo SQL code to show where you want the arguments to be used, and how and where you intend to use the IF clause?

    I know you mean something more complete than the following example:
    dim session.userid as c (assuming this stores the userid and is populated upon login)
    dim cn as sql::connection
    dim args as sql::arguments
    cn.open("::name::conn")
    vsql = "SELECT * WHERE userid = :userid"
    args.add("userid",session.userid)
    cn.execute(vsql, args) 'omitted error trapping
    ... use results
    cn.close()
    Steve Wood
    Join the ALPHA DEVELOPERS NETWORK
    There is no Cloud. It's just someone else's computer.
    Web - Mobile - Hosting - Products - Frameworks - Developer Resources
    AlphaToGo | IADN (100% Alpha Anywhere Websites)

    Comment


    • #3
      Re: Why does AA not support arguments directly in field SELECT statement?

      you could do it if you put the if clause outside of sqlSelect statement.
      thanks for reading

      gandhi

      version 11 3381 - 4096
      mysql backend
      http://www.alphawebprogramming.blogspot.com
      [email protected]
      Skype:[email protected]
      1 914 924 5171

      Comment


      • #4
        Re: Why does AA not support arguments directly in field SELECT statement?

        Steve,
        I should have been more specific, it is various places in the AA Builders that I run into trouble if arguments are referenced when defining columns for output, either to be output directly or to be used in an alphaDAO "IF" statement. For example, when building the SQL Statement for a ViewBox, the ViewBox fails to build the list of "Fields" if an argument is used anywhere in the SELECT clause. If I'm adding a ViewBox with a connection to NorthWinds and I have an Argument for the UX defined as gRegion (character) then the following SQL statement causes the ViewBox to not list any entries in the "Fields" list:

        Code:
        SELECT CustomerID,  If( Region = :gRegion , 'Y', 'N')  AS Expr1, CompanyName, ContactName, ContactTitle, Address, City, Region 
        FROM Customers


        Gandhi,
        Yes, but adding what I need outside of the SELECT clause means I have to add a table using CROSS JOIN (which the AA SQL Genie builders do not support) or add a FULL OUTER JOIN where I relate the key field in the joined table to a hard-coded constant, like 'primary_key_field > 0' (which really seems like improper SQL) and add my argument into the WHERE clause.

        Comment


        • #5
          Re: Why does AA not support arguments directly in field SELECT statement?

          I'm by no means a SQL expert so, for what it's worth, could you use CASE to accomplish what you want?

          SELECT CustomerID, CASE WHEN Region = :gRegion THEN 'Y' ELSE 'N' END AS Expr1, CompanyName, ContactName, ContactTitle, Address, City, Region
          FROM Customers
          Mike Brown - Contact Me
          Programmatic Technologies, LLC
          Programmatic-Technologies.com
          Independent Developer & Consultant

          Comment


          • #6
            Re: Why does AA not support arguments directly in field SELECT statement?

            It's a bit of a complex statement. Easily addressed in MySQL or SQL Server... but not everywhere in Alpha builders. Instead, just fake out the builder to get the ViewBox built... and then put back your if statement. Also... it's not a matter of a good SQL Statement or not... or whether you use IF or CASE... but what the builder understands and can parse.

            Use this statement for the builder...

            Code:
            SELECT CustomerID, 'Y' AS Expr1, CompanyName, ContactName, ContactTitle, Address, City, Region 
            FROM Customers
            You'll now have your fields. Then build out the ViewBox. When you have your layout and other stuff set... add back the if statement.

            You didn't specify what how your argument was put together... may not matter.

            Comment


            • #7
              Re: Why does AA not support arguments directly in field SELECT statement?

              Backing up Mike's comment, here is an update statement using CASE.

              vsql = <<%txt%
              UPDATE project_requests SET
              status = CASE WHEN :new_status <> 'Open' THEN 'Closed' ELSE 'Open' END,
              status_detail = CASE WHEN :new_status <> 'Open' THEN :new_status ELSE NULL END,
              closed_date = CASE WHEN :new_status <> 'Open' THEN :closed_date ELSE NULL END
              WHERE id = :id
              %txt%
              Steve Wood
              Join the ALPHA DEVELOPERS NETWORK
              There is no Cloud. It's just someone else's computer.
              Web - Mobile - Hosting - Products - Frameworks - Developer Resources
              AlphaToGo | IADN (100% Alpha Anywhere Websites)

              Comment


              • #8
                Re: Why does AA not support arguments directly in field SELECT statement?

                Switching the SQL to native syntax in the SQL Genie Builder does not help; parts the of the builders still refuse to handle arguments in the column list section of the SQL SELECT statement.

                What is strange, to me, is that the inner levels of the SQL Genie Builder know how to execute the SQL and prompt for any arguments that are used. But, when you get to the outer levels of the builders (like the ViewBox Builder "Data Source" tab) the IDE totally forgets to prompt for and build arguments and the query apparently fails with an internal error that is not shown and it does not repopulate the list of fields to display on the "Fields" tab. If the "Fields" tab was previously built when the SQL did not contain arguments then you will see the fields from the previous SQL that worked.

                Comment


                • #9
                  Re: Why does AA not support arguments directly in field SELECT statement?

                  Not really sure which part you're working in... but in the ViewBox, creating a CustomerSQLStatement without your "if" clause... in order to build out the ViewBox, and then adding back the "if" clause... works.

                  Comment

                  Working...
                  X