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

Performance Dilemma: Repeating Section v. Insert Statement

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

  • Performance Dilemma: Repeating Section v. Insert Statement

    Hi All,

    I have a fairly large UX that is bound to two tables, which have a one-to-many relationship. The child table is populated via a HIDDEN repeating section in the UX. While this works just fine, its slower than I would like. Without getting into a tremendous amount of detail (which may be unavoidable, but I'll try), I'm wondering if, instead of the repeating section, it would be faster to execute an INSERT SQL statement via an xbasic function to insert the records into the appropriate table. I haven't taken this path yet, simply due to lack of time, but would be willing to if there is a good chance it could improve over all performance.

    Thoughts?

    Thanks,
    Scott

  • #2
    Re: Performance Dilemma: Repeating Section v. Insert Statement

    I would certainly think a direct callback would be faster... you're cutting out the middleware.

    Comment


    • #3
      Re: Performance Dilemma: Repeating Section v. Insert Statement

      Insert statement.

      Especially if it is a hidden UX - Then there would be no reason to put the data to the screen at all. If you need to keep track of a total for the hidden UX, you can do that with a select statement too.

      Caveat: part of the question is WHEN do you want to save the data. IF they are entering a bunch of records into the hidden UX, then saving it all at once (or possible not saving!), insert statements might not help a whole lot.

      You have to store the data SOMEWHERE until you save it, might as well be a repeating section.

      However, if you are literally putting records into the UX and submitting at the same time, then you might as well insert them right away.

      Note: You may also have to write update/delete statements too, don't know what you really need.

      Comment


      • #4
        Re: Performance Dilemma: Repeating Section v. Insert Statement

        The child table is populated via a HIDDEN repeating section in the UX
        how is the data inserted into the repeating section if hidden, if it done automatically drawn from somewhere in the parent section then why not consider stored procedure. all will be done at the db level, i am sure it is faster than alpha updating.
        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


        • #5
          Re: Performance Dilemma: Repeating Section v. Insert Statement

          Thanks all - great suggestions and considerations. Given the comments, it seems like the insert statement is the way to go!

          Comment

          Working...
          X