Kalu,
The user interface in MapInfo Pro is, as you and Peter noted, only looking at the base table. In the case of the layer control, it is just showing a possible override style for each possible type of geometry. That is the only metadata we currently have. There is no such corollary for a query unless you save the results as a separate table. In a query, we don't copy the data so we don't even have a temp table metadata to look in.
In the case of large tables, it would take a potentially long time to read each record and build up the same metadata that comes more or less for free in a basetable.
That said, it does not mean that it would always be slow to do this. I could imagine an option where we would do the query and update the UI. But that does not exist today so it would be a feature request.
By the way, if you were to edit one of those records and change the point to a line, it would immediately display in the override style that does nothing right now. So it kind of has a purpose.
------------------------------
Eric Blasenheim
Spectrum Spatial Technical Product Manager
Troy, NY
------------------------------
Original Message:
Sent: 01-14-2020 16:59
From: Kalu Ribush
Subject: MapBasic v2019
Thanks Peter,
I'd be interested to hear if we can get this working for queries too.
I can see if I have a table with mixed geometry, and I query the records for different geometries as separate layers, in the layer control the icons for all the geometries are shown for each query layer, either though q_poly only has polygons and q_point only has points.
------------------------------
Kalu Ribush
Senior Mapping Specialist
Department of Economic Development, Jobs, Transport and Resources (DEDJTR)
Melbourne
Original Message:
Sent: 01-14-2020 03:34
From: Peter Horsbøll Møller
Subject: MapBasic v2019
Hi Kalu,
Yeah, I imagine we get that information from the MAP file and therefor a query will copy the predominant style form the base table.
In most cases that would be fine. But if you have a table with mixed object styles, the predominant object type can certainly be misleading for certain queries.
I'll leave it to the developers if we can change the behavior to return the predominant object types from queries too. @Bob Fortin, @Anshul Goel, any ideas if this can be changed?
------------------------------
Peter Horsbøll Møller
Distinguished Engineer
Pitney Bowes Software & Data
Original Message:
Sent: 01-13-2020 19:43
From: Kalu Ribush
Subject: MapBasic v2019
Hi Peter
Some nice additions.
I've tested the TableInfo() function to get predominant object type. This appears to only work on base tables - if I use this on a query result, it doesn't tell me the predominant type in the query (instead it gives me the result for the table the query is based on). Is this working as designed or is this a bug? Other TavbleInfo() functions give different results for base tables and their queries.
Kalu
------------------------------
Kalu Ribush
Senior Mapping Specialist
Department of Economic Development, Jobs, Transport and Resources (DEDJTR)
Melbourne
Original Message:
Sent: 01-10-2020 03:11
From: Peter Horsbøll Møller
Subject: MapBasic v2019
We have released MapBasic v2019.
You can find and download it here: MapBasic v2019
Amongst the new features you will find:
- Improved SQL syntax, like table alias, LIMIT keyword, improved join capabilities and where expressions support for Delete and Update statements
- Getting a tables predominant object type via the TableInfo() function
- Access to 15 more preferences via the GetPreference() function
- -New attributes for the SystemInfo() and MapperInfo() functions
- New Atan2() function
------------------------------
Peter Horsbøll Møller
Distinguished Engineer
Pitney Bowes Software & Data
------------------------------