Changes between Version 2 and Version 3 of 60MigrationIssues

Timestamp:

Sep 1, 2010, 8:59:46 PM (14 years ago)

Author:

sdlime

Comment:

--

60MigrationIssues

@@ -14 +14 @@
 '''CGI Query Mode Changes'''
 
-  - remove all ...MAP modes (e.g. ITEMQUERYMAP). They just bloat the code and documentation. A suitable alternative has existed since 5.4, that is, use a base mode coupled with an image query format (e.g. ...&mode=itemquery&qformat=png24&...).
+  - remove all ...MAP modes (e.g. ITEMQUERYMAP). They just bloat the code and documentation. A suitable alternative has existed since 5.4, that is, use a base query mode coupled with an image query format (e.g. ...&mode=itemquery&qformat=png24&...).
 
+
+'''Support for STYLEs in LABELs'''
+
+  - this was added at the NYC code sprint. It allows you to define markers and label boxes using styles so you can do things like road shields and complex line work in one pass. This means all the attributes associated with label billboards and billboard shadows can be removed. This simplifies the labelObj and everything associated with it. Simply deprecating the parameters would add undue complexity to the label handling code.
+
+'''One-pass Query Handling in MapScript'''
+
+  - I screwed this up in 5.6 by introducing the resultsGetShape() method to layers. Only to find out later that the drivers didn't implement things the same way. I propose reverting to a single getShape() method and requiring both passed indexes (if the user wants performance). The first index would be the global shape index suitable for random access to a shape at any time. The second, tile index, would be interpret differently but only one of two ways:
+
+    1. If a driver supports tiling (basically only shapefiles) then it's truly a tile index and handled as such.
+    2. If a driver doesn't support tiling the index would be interpreted as an index relative to the current result set.
+
+So, for a driver in case 2, it would look at the second index value and decide how to behave (globally or locally). This is basically how it works now, we just need to merge things into a single getShape() method for Oracle and PostGIS drivers. Ultimately this will make users happy and opens up possibilities for supporting two types of query caches (parameters vs. global indexes).
+
+'''CGI Run-time Validations'''
+
+  - Run-time substitutions are popular and powerful. They also can be used as a route to sql-injection if not used properly. We offer users a way to set default values and value validation but neither are required. I propose changing the latter and not performing substitutions unless a validation is explicitly defined. We do this now for URL-based parameter override.