Well, after some testing I found out that qgis now can open dbf files as vector layers. It's enough for me to create the "relate" implementation. <br>As far as I can see, it's possible and won't take too long to implement. Will it be usefull? Is anyone already working on a full join implementation?<br>
Mauricio de Paulo<br><br><div class="gmail_quote">2009/12/26 Maurício de Paulo <span dir="ltr"><<a href="mailto:mauricio.dev@gmail.com">mauricio.dev@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi folks,<br>I don't remember exactly what was defined on the last discussion about table joins.<br>I've read many good sugestions, many of them about implementing attribute relationship inside qgsvectorprovider.<br>
I also work on ArcGIS and the relations and joins on ArcGIS usually don't show the full table join. It only shows the related attributes of a single feature. So for each feature, you can use a Info tool to see every attribute about it (including the ones that comes from related tables). Everything is done on the fly, but performance is not a big issue as i'm only going to search for one feature's relationships.<br>
I'm using the screenshots that are attached to the mail as an example of how it should work.<br>At the moment I need some feedback on what it is or is not a good approach and if it's gonna be usefull for the users.<br>
What do you guys think?<br>The idea is a plugin to record what relationships are stored for each layer and then show the attributes in a tree view where a single feature can be linked to many other rows in the second table. I still don't know how i'm going to implement it but either I will use ogr or qgsvectorprovider. I still have to search if it's possible to access the dbf files and postgis connections using qgis api.<br>
Any comment is welcome.<br>Mauricio de Paulo<br><br><br><br>
</blockquote></div><br>