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

Delete Taking Long Time

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

    Delete Taking Long Time

    I have created a 'Delete' operation for a table. There are 78,000. records. I have created an index on the field that I am basing the delete query on. The table is not open when I run the delete operation.

    Question: Is it normal for Alpha to take 4 - 5 minutes to find the records to be deleted (~10,000) and then another 4 - 5 minutes to actually delete the records?

    #2
    RE: Delete Taking Long Time

    I don't think it should take that long.How are you doing it? With an index on the field for the delete query, you should use the between function to get the records and delete_range() to delete them. Something like
    t=table.open("tablename")
    t.order("FieldName","Between(FieldName,'"+value1+"','"+value2+"')")
    t.delete_range()
    t.close()
    should work pretty fast if FieldName, value1 and value2 are all character.

    Finian
    Finian

    Comment


      #3
      RE: Delete Taking Long Time

      Thanks for your response...

      I am trying to delete records that satisfy the following condition:
      ElemlinkLeft(Repslink,14) = .t.

      When I create a 'delete reecords'operation & specify the above criteria (or specify a saved Query with the same criteria) the delete takes forever!

      I have since discovered that if I perform a Query operation (with the above criteria), followed by a 'delete selected' operation it goes so fast that I can hardly see the little worm in the scroll bar.

      This has solved my problem, but I still wonder why I can't do it in 'one swell foop'.

      David

      Comment


        #4
        RE: Delete Taking Long Time

        This has solved my problem, but I still wonder why I can't do it in 'one swell foop'.

        Perhaps the one case exploits an index while the other doesn't?

        Comment


          #5
          RE: Delete Taking Long Time

          Perhaps...
          But... I created an index on the ElemLink field (the field used for in the criteia for the Query & delete).??

          Based on your hypothesis... when the two separate operations execute (Query followed by Delete Selected) the index IS used... BUT when I try to create an operation that deletes records, based on exactly the same criteria used in the Query, the index is not used???

          Is there some way to force the operation that deletes based on a saved query to use an index??

          If Alpha is using an index in the separate Query Operation but not in the combined one (with no delete) I don't know why... any ideas?

          Comment


            #6
            RE: Delete Taking Long Time

            Based on your hypothesis... when the two separate operations execute (Query followed by Delete Selected) the index IS used... BUT when I try to create an operation that deletes records, based on exactly the same criteria used in the Query, the index is not used???

            That's my theory, yes.

            Is there some way to force the operation that deletes based on a saved query to use an index??

            I don't know much about operations yet, but it looks like a pretty closed box.

            If Alpha is using an index in the separate Query Operation but not in the combined one (with no delete) I don't know why... any ideas?

            Again, speculating: While the end result of your two approaches, the internal logic used to get there is NOT the same. The operation may take longer because it works even if there is no index, where your query approach will not. It might not be a simple matter for the operation code to check for indices at all possible points where they might benefit the task at hand.

            This sort of thing happens in computing a lot. Until the mid-'90s, the best way to get the fastest code was to write it in assembler. As compiler technology improved and the underlying CPU got more complex, it got harder and harder to improve by hand on what a compiler could do.

            Think of it this way: A5 provides a solution that works in all cases, and a solution that works faster if you know how to apply it.

            Comment


              #7
              RE: Delete Taking Long Time

              >>end result of your two approaches

              Doh.

              Should've been "end result of your two approaches is the same".

              Comment

              Working...
              X