[Qgis-developer] Thoughts about multi-type tables in QGIS

[Régis Haubourg]

olivier wrote
> 
>> to me it sounds a bit like loading "varchar" and "float" in the same
>> column
> 
> 
> That's exactly what it is not. Generic geometry is a valid and well
> defined
> type, and postgis functions behave very well with it. ST_Area for instance
> will return 0 for a point or a line, which is an accurate result and makes
> sense.
> And while some functions are type-specific, most functions work and make
> sense on all types (spatial relations, buffer, bounding boxes, validity,
> transformation, simplification, conversion...).
> 
> If you split your data in different tables (or columns), you loose the
> ability to use any of those functions on all your records at once (without
> some complex query that won't be doable in QGIS UI), which IMO is really a
> pity...

 Hi , to me, most QGIS geometric operators assume one geometry type. Can you
explain what king of generic operation you have in mind ? 

I think that doing this will generate a complete refactoring of:
- all processing scripts
- all ftools 
- all plugins assuming one geometry.

Again, I can't see from how in QGIS GUI that can improve things for most
users, without making it more heavy and complex. And that would be very
costy. Any mockup welcome, that can help me change my opinion.. 
All the best, 
Régis




--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Thoughts-about-multi-type-tables-in-QGIS-tp5196607p5200245.html
Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.