Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Revisions: Issue #17913 All Revisions ] Back to Issue ]
Summary 0017913: Navigation to blank tab
Revision 2011-07-06 10:31 by alostale
Description Direct navigation to related objects results in a blank page in some occasions.

This can happen when the number of records in the destiny table is big enough and the default sorting column for that tab does not do a deterministic order.

When doing the navigation, it is not only loaded the selected record but a set of records that must contain the selected one. This is done to be able to switch to grid view quickly. In order to do it 2 queries are executed to DB: 1st one to determine the position of the selected record and 2nd one to get the actual data limiting the results to a number (100) of records that includes the selected one.

In the case described above, it can happen 2nd query doesn't order in the same way 1st one does. If this happens and the 2nd query does not include selected record, tab is shown blank.

Workaround: when this happens it can be easily solved by using a sort column (Record Sort No. in tab) one which is unique (i.e. document no) so it makes the order deterministic.
Revision 2011-07-06 10:02 by alostale
Description Direct navigation to related objects results in a blank page in some occasions.

This can happen when the number of record in the destiny table is big enough and the default sorting column for that tab does not do a deterministic order.

When doing the navigation, it is not only loaded the selected record but a set of records that must contain the selected one. This is done to be able to switch to grid view quickly. In order to do it 2 queries are executed to DB: 1st one to determine the position of the selected record and 2nd one to get the actual data limiting the results to a number (100) of records that includes the selected one.

In the case described above, it can happen 2nd query doesn't order in the same way 1st one does. If this happens and the 2nd query does not include selected record, tab is shown blank.

Workaround: when this happens it can be easily solved by using a sort column (Record Sort No. in tab) one which is unique (i.e. document no) so it makes the order deterministic.


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker