Sounds like a bug, I suspect that your db combo is more rare and not many people have tried it yet. Ask on the developer list or file a ticket on hub.qgis.org
thanks, Alex On 03/07/2014 07:24 AM, James Wood wrote: > Just wanted to float this one again to see if anyone had any feedback. > > Thanks, > > ---------- Forwarded message ---------- > From: James Wood <[email protected]> > Date: Sun, Mar 2, 2014 at 10:43 AM > Subject: Relationships and SQL Spatial as Child > To: QGIS-User Mailing List <[email protected]> > > > Hello QGIS Users, > Just wanted to know if anyone else has run into this... > I'm running QGIS 2.2 x64 (OSGeo4W installer) on Windows 7 SP1. > > When trying to utilize the new Relations piece (which is a GREAT addition), > I can establish relationships and have them work perfectly except when the > child (or referencing layer) is in my SQL Express 2012 database. I set up a > test project with identical address points and parcel layers in PostGIS, > SpatiaLite and SQL. I can get any combination to work, but when the child > layer is in the SQL db it will not. > > A picture is worth a thousand words, so I took some screenshots: > > > > > > > I've double-checked the linking ID field for the parcels and it is always a > 1:1 with the address point I have identified. However, just to be sure it > wasn't something funky with the parcel base, I established a link between > the address points and an aed (defibrillator) point layer that I had with > the same result. I also tried establishing a relationship with a > non-geometry table in another db in the same instance without any luck. > > > I'll be interested in your feedback... > > Thanks, > James > > > > _______________________________________________ > Qgis-user mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/qgis-user > _______________________________________________ Qgis-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-user
