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

MySQL Duplicate Insert

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

    MySQL Duplicate Insert

    I ran into an issue I've never seen before (granted, my experience is relatively limited) and wanted to ask if anyone else has ever seen anything like this.

    I'm using the latest version of AA and the problem revolves around inserting records from a ReadOnly Grid/Updateable Detail form into a MySQL table (AlphaDAO). A user reported that when browsing the database they noticed a record that seemed to be appearing twice (the primary keys, which are AI, were one after the other). I examined the records through MySQL Workbench and saw that the data (including a timestamp down to the millisecond) were identical, except of course that the primary keys were different. We are logging MySQL activity so I examined the log and saw two INSERT statements being executed with exactly the same data, again down to the full timestamp. There were only about 70 statements in between, so not enough time for a user to deliberately enter a duplicate (not that I think that's a possibility anyway).

    Has anyone run into this sort of thing, either in the context of Alpha or any other?

    I would appreciate any "enlightenment", at this point I don't know where to start troubleshooting this.

    #2
    Re: MySQL Duplicate Insert

    It has been revealed as a possibility and is addressed in the pre-release documents and corrected in the latest pre-release code, where alpha has a file keeping track of synchronized events. So yes it is possible in the current official release build.
    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: MySQL Duplicate Insert

      Originally posted by peteconway View Post
      It has been revealed as a possibility and is addressed in the pre-release documents and corrected in the latest pre-release code, where alpha has a file keeping track of synchronized events. So yes it is possible in the current official release build.
      Ahh, I see, thanks for the post. This is actually a pre-release build (which the client wanted, they're aware of the possible issues) and the double insertion seemed to occur around an entry in the synchronization log (which you alluded to). I will update to the latest pre-release build, I mean, it couldn't hurt.

      For some reason, I feel better now (I don't know why). :)

      Comment


        #4
        Re: MySQL Duplicate Insert

        If you still have the issue send a bug report to the pre-release email address.
        Insanity: doing the same thing over and over again and expecting different results.
        Albert Einstein, (attributed)
        US (German-born) physicist (1879 - 1955)

        Comment


          #5
          Re: MySQL Duplicate Insert

          OK, but I'm on 3356-4599 so I'll update to the latest build so we're talking apples and apples.

          Just to be clear, this problem did NOT involve a synchronization request, it was a straight insert from a grid/detail form (I think I mentioned that anyway in my initial post). I scoured the prerelease notes and the only mention of duplicates was in connection with the synch log table. Now, granted, noticed in the MySQL log that there was an insert to the synch log table just before this issue cropped up, but the record(s) in question were not the ones involved in that insert.

          Again, thanks for the info and I'll keep close watch and send a report should this thing crop up again, after I've updated.

          Comment

          Working...
          X