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

SQL Rollback

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

  • SQL Rollback

    I have seen some of the posts about the sql commit and rollback using the conn.BeginTransaction(), conn.CommitTransaction(), conn.RollbackTransaction(), etc.
    I am still not able to rollback once I insert a transaction. Is there any setup that needs to be done on Alpha Properties (UX properties, etc) or on MYSQL server to enable SQL transactions?

    Regards!
    Last edited by Mkpatil; 06-30-2015, 12:26 PM.

  • #2
    Re: SQL Rollback

    I have noticed that if I use a select statement after starting a Transaction [conn.BeginTransaction()] I am getting the following error
    conn.BeginTransaction()
    Insert ...
    update ....
    select .... <<<<<<<< Error here
    Insert ...
    update ....
    conn.CommitTransaction()
    ERROR:
    Database API specific error Your database has returned the following error code and description to Alpha Five. Consult your database documentation for further information.2014 - 'Commands out of sync; you can't run this command now'
    Can I not use a select to check something before further inserts in a transaction?

    Regards!

    Comment


    • #3
      Re: SQL Rollback

      Please see this note. Appears transactions will be negated if a select is used

      http://www.alphasoftware.com/alphafo...ginTransaction
      Regards,

      Kotin Karwak
      Developer Edition
      Version 12.3 Build 2684
      System Addins: Build 4438
      Build machine Windows Vista
      Skype: mateso08

      Comment


      • #4
        Re: SQL Rollback

        Thanks Kotin.

        My transaction has few inserts, but before I do each, I need to check something (latest) with a select, I wonder how I can do that then.

        Regards!

        Comment


        • #5
          Re: SQL Rollback

          Not much db work myself but assume, the transaction begin/end can just surround the operation, I.e update. All the selects and logic can sit outside that construct.
          Regards,

          Kotin Karwak
          Developer Edition
          Version 12.3 Build 2684
          System Addins: Build 4438
          Build machine Windows Vista
          Skype: mateso08

          Comment


          • #6
            Re: SQL Rollback

            Originally posted by Mkpatil View Post
            Thanks Kotin.

            My transaction has few inserts, but before I do each, I need to check something (latest) with a select, I wonder how I can do that then.

            Regards!
            Use multiple connections?
            Al Buchholz
            Bookwood Systems, LTD
            Weekly QReportBuilder Webinars Thursday 1 pm CST

            Occam's Razor - KISS
            Normalize till it hurts - De-normalize till it works.
            Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
            When we triage a problem it is much easier to read sample systems than to read a mind.
            "Make it as simple as possible, but not simpler."
            Albert Einstein

            http://www.iadn.com/images/media/iadn_member.png

            Comment


            • #7
              Re: SQL Rollback

              Thanks Kotin & Alan!

              I did not know I could have multiple connections
              Dim conn as sql::Connection 'connection for inserts and may be
              Dim conn2 as sql::Connection 'connections for selects

              I may try that out.
              I was also trying to do all the selects etc (checks and balances) before hand, and prepare a bunch of inserts and when ready sending these inserts as one transaction using conn.BeginTransaction().
              The risk here is that, if a record from another user gets inserted right after I complete my checks and balance and before I start the transaction. I am checking how to lock few records before I start my checks and balances and automatically release the lock when I commit.

              Regards!

              Comment


              • #8
                Re: SQL Rollback

                Fyi- The risk with multiple connections is that, the uncommitted records in connection 1, remain invisible in (selects of) connection 2. So I will not get the right totals using the select, unless I keep a running total of what I inserted that are still uncommitted and include them in my calculations. Appreciate your input.

                Regards!

                Comment


                • #9
                  Re: SQL Rollback

                  I think your approach is correct, it is my understanding that you could have one or more
                  insert, update, delete and select statements in a begin and end transaction code block.
                  if some statements did not get transacted (if there is an error) the rollback should work. so if your select statement gets executed then there is no error you cannot rollback.
                  it is also my understanding that you cannot manually rollback if you check a condition in that code block, it has to be an error in execution of the statements.
                  I could be wrong in my understanding.
                  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


                  • #10
                    Re: SQL Rollback

                    Thanks Gandhi.
                    I use either rollback or commit depending on how the updates were executed, so both may be used. If one of the insert failed, then I just rollback all the inserts.
                    The code is as shown (but little more efficient, because I jump out when the first insert failed)
                    conn.BeginTransaction()

                    heading_to_rollback = "N"

                    sqlSelect = "INSERT INTO ..."
                    result = conn.Execute(sqlSelect,args)
                    if (conn.AffectedRows() = 0) then
                    heading_to_rollback = "Y"
                    end if

                    sqlSelect = "INSERT INTO ..."
                    result = conn.Execute(sqlSelect,args)
                    if (conn.AffectedRows() = 0) then
                    heading_to_rollback = "Y"
                    end if

                    sqlSelect = "INSERT INTO ..."
                    result = conn.Execute(sqlSelect,args)
                    if (conn.AffectedRows() = 0) then
                    heading_to_rollback = "Y"
                    end if

                    if (heading_to_rollback = "Y") then
                    conn.RollbackTransaction() ' ROLLBACK ALL
                    else
                    conn.CommitTransaction()
                    end if
                    Regards!

                    Comment


                    • #11
                      Re: SQL Rollback

                      I think these are all independent statements they get executed regardless, I am wondering if you can try something like this.
                      Code:
                      sqlStatement1 = "something"
                      sqlStatement2  "something"
                      sqlStatement3 ="something"
                      
                      open connection
                      begin transaction
                      result = cn.execute(cn, sqlStatment1)
                         if result then
                                result = cn.execute(cn, sqlStatment2)
                                  if result then
                                       result = cn.execute(cn, sqlStatment3)
                                            if result then
                                                commit transaction
                                          else
                                          rollback transaction
                                   else
                                   rollback transaction
                       else 
                       rollback transaction
                       end if
                      something like this, does it make any sense?
                      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


                      • #12
                        Re: SQL Rollback

                        Thanks Gandhi.

                        I am just having issues doing a select in between inserts to check something. Otherwise the inserts all get committed, or none based on the command I give.

                        So, I still think none will get executed if one of them fails. I have written code where it rollbacks whenever I program it to rollback even after some records were inserted.

                        In this example below I fail the second insert (say invoice header) statement 2 below by using 1=2 clause, the first Insert (say invoice line) runs fine with 1=1, then at the end it rollbacks even the inserted one. Try it.

                        Table creation:
                        CREATE TABLE `temp123` (
                        `Id` int(11) NOT NULL AUTO_INCREMENT,
                        `N1` int(11) DEFAULT NULL,
                        `C1` varchar(25) DEFAULT NULL,
                        PRIMARY KEY (`Id`)
                        ) ENGINE=InnoDB AUTO_INCREMENT=230 DEFAULT CHARSET=utf8;
                        function functionajaxsql3 as c (e as p)
                        Dim cn as sql::Connection
                        Dim result as l
                        Dim sqlSelect as c
                        Dim args as sql::Arguments
                        Dim rs as sql::ResultSet
                        Dim rows as N = 0
                        Dim value1 as N
                        Dim heading_to_rollback as C = "N"

                        functionajaxsql3 = "alert('Starting');"
                        result = cn.Open("::Name::Connection1")
                        if result then
                        if cn.BeginTransaction() then
                        args.add("args_N1","1")
                        args.add("args_C1","OK VALUE")

                        sqlSelect = "INSERT INTO temp123 (N1,C1) (select distinct '1', 'A' from websecurityusers where 1=1)"
                        result = cn.Execute(sqlSelect,args)
                        functionajaxsql3 = functionajaxsql3 +"alert('cn.AffectedRows() = " + cn.AffectedRows() + "');"
                        if (cn.AffectedRows() = 0) then
                        heading_to_rollback = "Y"
                        end if

                        args.clear()
                        args.add("args_N1","2")
                        args.add("args_C1","OK VALUE")
                        sqlSelect = "INSERT INTO temp123 (N1,C1) (select distinct '2', 'B' from websecurityusers where 1=2)"
                        result = cn.Execute(sqlSelect,args)
                        functionajaxsql3 = functionajaxsql3 +"alert('cn.AffectedRows() = " + cn.AffectedRows() + "');"

                        if (cn.AffectedRows() = 0) then
                        heading_to_rollback = "Y"
                        end if

                        args.clear()

                        if (heading_to_rollback = "N") then
                        if cn.CommitTransaction() then
                        functionajaxsql3 = functionajaxsql3 + "alert('Committed - test');"
                        end if
                        else
                        if cn.RollBackTransaction() then
                        functionajaxsql3 = functionajaxsql3 + "alert('Rollbacked - test');"
                        end if
                        end if
                        end if
                        cn.close()
                        end if
                        end function

                        Regards!
                        Last edited by Mkpatil; 07-02-2015, 03:08 PM. Reason: Remove args not used here

                        Comment

                        Working...
                        X