MapInfo Pro

Welcome to the MapInfo Pro community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Here are some useful links where you can find more information:

Product Announcements  Product Documentation  Ideas Portal

Discussions

Members

Resources

Events

 View Only

  • 1.  Selections on "Linked" or "Live" table shuffled after refreshed from source

    Posted 12-14-2017 21:17

    Hi,

    I'm not sure if this has been fixed or not. I have an environment that has PG + MapInfo?. When I make a selection from a certain "Linked" table either by manual or by query or by filter, then I would make some changes to some of the records on the selection, then when I hit save, it'll save to database but will ask "if I want to refresh current table or not", in most cases, I would say 'yes'. After refreshing, the original selection (that I mentioned above) would get reshuffled. Is this something that can be fixed?

    Some facts about the issue:

    • Is the numeric order is changed or the actual selection records are changing?

     Answer: The actual selection records will change.

    • What is “PG +” ? is this Postgres?

      Answer: PostgreSQL

    • What is Database version?

     Answer: 9.2

    • What is MapInfo Pro version?

     Answer: MapInfo v15 (32bit)

    • What OS are you using?

    Answer: Windows 7

    Thanks,

    Ferhad 



  • 2.  RE: Selections on "Linked" or "Live" table shuffled after refreshed from source

    Employee
    Posted 01-05-2018 07:43

    Hi Ferhad

    Sorry that we haven't replied to this question already.

    This issue is connected to the way MapInfo Pro works with selections on tables. MapInfo Pro only stores the RowIDs of the records in the selection/query.

    Now if the base table changes, that is the order of the records change, the selected elements will also change because what was earlier RowID 5 suddenly has changed to become RowID 6 and is no longer in the query.

    One way of changing this - and I'm not srure how possible that is - would be to start using the Primary Key from the database table in stead of the ROWID for DBMS tables that have a Primary Key. Often the Primary Key is named MI_PRINX but that's not a requirement.

    The Primary Key is static and unique thoughout the table but it might not be as fast to work with internally in MapInfo Pro.



  • 3.  RE: Selections on "Linked" or "Live" table shuffled after refreshed from source

    Posted 01-14-2018 22:09

    Sorry, guys if I made some confusions. I meant to say that when I apply a filter criteria on browser table and then when I do some updates, save the table and respond "yes" for "Refresh?", and then the filter that I applied previously would go away.

     

    ?



  • 4.  RE: Selections on "Linked" or "Live" table shuffled after refreshed from source

    Employee
    Posted 01-15-2018 04:14

    Ah, that might be the way it has been designed.

    If you make changes to a table, the filter/sorting of a browser is also affected.

    Maybe we need to revisit this and see if it can be improved