So inspecting the field names and scrolling through the data is often fruitful to understand the structure of the data. So it's less of an issue of finding a particular record but exploration to know if the data are structured to answer the question I have. I'll develop a hypothesis about the data structure and check against other sources and ask for peer review.
Those are all good things. Nothing about how scroll bars behave in Radian is a bar to doing them. You can do all of the above in Radian as well. It's just that scroll bars have much less utility when you are working with larger tables, especially if they are coming in from some external data source. I'd also recommend getting familiar with table navigation shortcuts like Ctrl-End and Ctrl-Home, and using Pg Up and Pg Dn when you want to scroll up and down through a table interactively. Hitting PgDn ten or fifteen times scrolls through a heck of a lot of records. Scroll bars can also be misleading. Someone might think "oh, I don't want to just see records from the beginning of a table, I want to jump to the middle for a different sort of sample." But that's an error because records in tables should never be assumed to be ordered. They often are, but that's a happenstance thing that no serious DBMS (not Oracle, not PostgreSQL, not DB2... etc, etc.) guarantees. If you want to look at records in order you do a query with ORDER BY. The way to get different, casual looks at parts of a table is to launch a command window and then in an ad hoc way write tiny queries. I'll often write multiple queries in a command window, copying and pasting extras, and then highlight the one I want and hit Alt-Enter to execute just that one. If you have a big table, the info pane will tell you how many records you have, or you can hit Ctrl-End to jump to the end and see how many records you have (and take a look at the "end" of the table...). Suppose it is 2000000 records. Write SELECT * FROM table OFFSET 1000000 FETCH 50; to take a look at 50 records from the middle of the table. Like I say, there's no order to be assumed but if you think there is or just want to sample records from the "middle" of the table, do that. For more than just a few records it is way easier to jump around in a table using OFFSET and FETCH than to try to approximate locations with a scroll bar. You can also do other queries, like Klaus suggests, to get your head around the table and the data it contains.
|