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



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 Temporary Data

  • Filter
  • Time
  • Show
Clear All
new posts

  • SQL Temporary Data

    I have the task of presenting information in a grid derived from a SQL backend where the results are further processed to create insert statements.

    The data is stored in Postgres for a vendor and the resultant data is inserted into a MySQL backend.

    I want to keep the MySQL backend as fast as possible as this is where the grid is attached.

    My problem is that multiple users will run the query with different results and I don't want to have other user's data inflate the record size. In other words, I don't want to get the results and insert them from all the different users into MySQL. I'm looking at the temporary table creation and was wondering if anyone has worked with temporary tables.

    One reason why I chose to move the data from one backend to the other is that there is some date data that is stored in a "tick" format that I convert to a date and time for the user to understand. The conversion takes place via an user defined function that is not accessible at the point of query. I also didn't want to mess with the vendor's database in terms of adding tables. I may get over it soon if this app takes to long to process the results.

    Anyways, any insight into PostGres or MySQL temporary tables is greatly appreciated. My app currently empties the table and inserts the results and I'm not sure this same process will affect other users when the app empties the temporary table as it appears the temporary table is unique to each session.
    Creating Healthcare Work-Flow Solutions Since 2005

  • #2
    Re: SQL Temporary Data

    A TEMPORARY table is visible only to the current connection, and is dropped automatically when the connection is closed. Not sure about PostGres, have only used MySQL. bear in mind users need create table privilledges when using this function.

    consider creating a server side function to
    a. mark records inserted by current user (in the current query)
    b. delete marked when finished

    although this has the effect of 'inflating' the file size, but i think the overhead is less than that of creating and deleting tables.
    also, the the filename of the new file has to be unique / non existent at the time of creating it. perhaps you can use a strong random generated filename ?!
    INFOMAS (Information Systems)


    • #3
      Re: SQL Temporary Data

      Not sure if I understand all, but I use temp tables a lot and I do not delete and re make them. I just empty and pack those tables for the next use as the data is no longer needed.

      Hope it helped.
      Dave Mason
      Skype is dave.mason46


      • #4
        Re: SQL Temporary Data

        you can only empty and pack .dbf tables built in with Alpha, DaveM, which quite rightly works well (for not so large database tables)
        Omagarc is using SQL as backend storage.
        INFOMAS (Information Systems)


        • #5
          Re: SQL Temporary Data

          Never found a table I could not empty, either on purpose or by mistake. LOL
          Dave Mason

          Skype is dave.mason46