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 Dual Primary Keys

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

    Sql Dual Primary Keys

    Hi everyone I have a table that has two primary keys with one of them being auto inc. The problem that I am having is it seems that the only type of sql table that supports this is Mylslam. Which is not the greatest for transactions due to the fact that it table locks every time that you do an insert. All of my other tables fly in comparison. Does anyone have any solutions or ideas.

    Remember two primary keys and one of those keys auto increments

    If entering a new record with store 1 the auto inc is 1 for the first entry and store 1 second entry is 2 but if its store two it starts a new auto inc at 1 and so on.

    Thanks in advance.
    Chad Brown

    #2
    Re: Sql Dual Primary Keys

    Hi, Chad, I don't understand why autoinc is behaving as you say. Is this mySQL that's doing the incrementing or Alpha?

    In any case it sounds like you'll have to do your own processing to maintain a separate unique identifier for each record. Seems like a redundant task to me.

    -- tom

    Originally posted by chadbrown View Post
    Hi everyone I have a table that has two primary keys with one of them being auto inc. The problem that I am having is it seems that the only type of sql table that supports this is Mylslam. Which is not the greatest for transactions due to the fact that it table locks every time that you do an insert. All of my other tables fly in comparison. Does anyone have any solutions or ideas.

    Remember two primary keys and one of those keys auto increments

    If entering a new record with store 1 the auto inc is 1 for the first entry and store 1 second entry is 2 but if its store two it starts a new auto inc at 1 and so on.

    Thanks in advance.

    Comment


      #3
      Re: Sql Dual Primary Keys

      maybe this helps:

      http://weblogs.sqlteam.com/jeffs/arc...mary_keys.aspx

      Comment


        #4
        Re: Sql Dual Primary Keys

        Tom I'm not sure what you mean about the behavior the auto-inc is working totally fine that is what its supposed to do ,just the speed is the problem, but if that's what you are referring to yes its weird to say the least. It is MySQL by the way. And sorry bea that doesn't help. I have searched a ton of stuff but keep coming up with nothing. The weird part is that if I enter something directly into the table it works quick maybe there is something on the Alpha side which is handling the mylslam table differently.
        Chad Brown

        Comment


          #5
          Re: Sql Dual Primary Keys

          Another thought maybe i go back to an inno db with just a timestamp and store id for the keys and not use an auto inc. perform a select statement to get the highest invoice number for that store in the table and add 1. Then create an index which uses store id and invoice number as unique. This would at least make the table maintain what I am looking for and maybe get my speed back. Seems like a round about way to have to do this being that Mylslam does this already but its locking the table for approx 25seconds for each new invoice which in today's standards is brutal.
          Chad Brown

          Comment

          Working...
          X