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

Issue with Outer Join in SQL Query

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

  • Issue with Outer Join in SQL Query

    We have a tabular grid developed in Alpha and we are using SQL query to fetch the data into the grid. The query is a combination of tables and views. It was working fine until we had to add an outer join to the query. We are getting error - 405 - 'line 3:50: unexpected token: (' Below is the Query that we are using. This query is perfectly working fine when running in toad. What is the issue with (+) in Alpha? Doesn't it support outer join this way? If not, what is the alternative solution for this? Can someone please guide us on this.

    Query:

    SELECT T.REF_ID, T.CR_ID, T.PNM_ID, V.CREATED_NAME, V.UPDATED_NAME, ITEM.LABEL, ITEM.LABEL_VAL, NOTE.PNM_ID, NOTE.PNM_DESC
    FROM TABLE_1 T, VIEW_1 V, VIEW_2 ITEM, TABLE_2 NOTE
    WHERE T.CROSS_REF_ID = V.CROSS_REF_ID(+) AND T.PNM_ID = NOTE.PNM_ID AND T.CR_ID = ITEM.LABEL_VAL(+)

  • #2
    Re: Issue with Outer Join in SQL Query

    LEFT OUTER JOIN vClearanceSaleHeaderInclusionImageGalleryDefault vClearanceSaleHeaderInclusionImageGalleryDefault
    ON ClearanceSaleHeader.ClrID = vClearanceSaleHeaderInclusionImageGalleryDefault.ClrID
    Copy was direct from my SQL Statement
    Insanity: doing the same thing over and over again and expecting different results.
    Albert Einstein, (attributed)
    US (German-born) physicist (1879 - 1955)

    Comment


    • #3
      Re: Issue with Outer Join in SQL Query

      Alpha? Doesn't it support outer join this way? If not, what is the alternative solution for this?
      i am not sure alpha supports it or not. and i am not even sure it is ansi compliant.
      the easier way to do will be explicitly stating left join(first) and right(second).
      you can also easily build the sql query in alpha too, if you like, and make the join type as you like it and test the query to see if the desired results are there and then build your grid based on that.
      Last edited by GGandhi; 05-24-2016, 06:38 AM.
      thanks for reading

      gandhi

      version 11 3381 - 4096
      mysql backend
      http://www.alphawebprogramming.blogspot.com
      ggandhi344@gmail.com
      Skype:ggandhi344@gmail.com
      1 914 924 5171

      Comment


      • #4
        Re: Issue with Outer Join in SQL Query

        If you are in a Grid you should be using Alpha's SQL syntax as generated by the Alpha SQL Genie. Grids do not have a property to go along with their SQL property to specify what format / syntax the SQL string is using. If you try to stuff your DB's native SQL into a Grid then you will eventually run into trouble, as you have seen here because Alpha cannot keep track of what it should use to parse the SQL: Alpha's Syntax or native db syntax. If you are working with a LIST in a UX then you will see that alpha has a "portableSQL" property to allow it to track what type of SQL is being used. I suggested to them that they do the same for a Grid, but I have not seen that happen yet.

        Since you are in a Grid, you should rewrite your query using the built-in Alpha SQL Genie.

        Comment

        Working...
        X